Introducing a new “+ Existing Users” button on the Team page of a project, an admin can now add multiple users or user groups to a project with a single project role.

Introducing a new “+ Existing Users” button on the Team page of a project, an admin can now add multiple users or user groups to a project with a single project role.
We’ve made several quality of life user management enhancements to assist in adding and updating user permissions. Admins will now have the enhanced ability to share files with other users, add users in bulk, and change the user types. These new features were designed to aid in seamless user management and administration on the platform as well as to enable user adoption and growth
Now, additional users can be updated in a single action in one location, without having to take the additional steps of adding them and then re-adding them to projects.
Introducing a new + Existing Users button on the Team page of a project, an admin can now add multiple users or user groups to a project with a single project role.
In the Add/Edit User dialog, there is a new option to select the user type for each user. The main user types being Admin (Customer Admin), Standard, and Guest.
This new feature is accessible in both the Users and Teams pages.
In version 3.6 it was not possible to convert a guest user to a standard user without deleting add re-adding the user. This feature addresses that issue and enables and admin to convert a guest user to a standard user.
SSO login capabilities have been added for customers on Saltmine. Previously, any SSO setup on platform needed to be handled individually and integrated. With this newest update, customers can login via SSO and not have to create a password on the Saltmine platform.
Multi-Factor Authentication note: Saltmine supports multi-factor authentication. But please note that, if the users log in via their SSO provider, then they will be redirected to their own multi-factor authentication. Only if the user uses a Saltmine password, then they would use Saltmine’s MFA.
Example:
Employee (with an @CustomerOrg.com email) would be able to log in using their company’s credentials (Saltmine Login Page→ Type Email → Redirected to Identity Provider Page→ Type Organization email and password → Redirected to Saltmine for completed login).
External vendors that do not have an @CustomerOrg.com email, will not go through those steps. Instead, they must create a Saltmine password with their emails.
Reach out to your Customer Success Manager to start the conversation!
*Please Note: For the best user experience, please push for OIDC over SAML integration.
Two possibilities of this happening:
Solution:
The email provided is authenticated by the IDP, but a user account with the email is not added to any Saltmine customer.
Solution:
The email provided is authenticated by the IDP, but a user account with the email does not exist in Saltmine app.
Solution:
In most cases, this is due to the user’s browser blocking the app from opening a new tab that facilitates the SSO re-login process, or the new tab is terminated preemptively by the user.
Solution: Enable pop-up/new tab by Saltmine in browser settings
In most cases, this is due to the user’s browser blocking the app from opening a new tab that facilitates the SSO re-login process, or the new tab is terminated preemptively by the user.
Solution: Enable pop-up/new tab by Saltmine in browser settings
Depending on which social login, SSO security configuration used by customer, customer’s SSO admin may need to grant Saltmine access to their resources. This needs to be done once only.
This could be a user error, mapping error, or incomplete integration.
Solution:
Question:
Does Saltmine support a Dual Authentication SSO? If dual authentication is not possible, we would basically need to create our outside vendors (architect designers, furniture supplier) as contractors to give them an org email that would need to be re-approved every 6 months.
Answer:
Assuming Saltmine sets up a customer’s identity provider ( E.g. Microsoft, Okta, Google, etc) – any employee logging in with an @(CustomerOrg).com email would login to the platform using their organization credentials.
Any other email domain, one that a contractor might use, will not go through the identity provider page, rather they would create a saltmine password with their emails (the current process). This method would avoid the need to re-approve a contractor’s customer org email every 6 months.