Allow creating users as "Active" instead of "Invited"
complete
L
Louis Bailleul
When syncing users from an external source it makes sense to create the users as "Active" and have a separate function to invite them.
This is particularly useful when designing a feature that manages teams and groups that needs access to the entire company user list but not all users are expected to access Port.
Gur Shafriri
Merged in a post:
Allow users to be not invited when added
K
Kevin Puventhiranathan
Today, when adding a new user to Port, using an SSO provider / the User blueprint with a data source - they must be invited and can sign in to the portal once you add them. It would be helpful if you could have these users as inactive and not invited, so that we will be able to present users & teams as part of the company hierarchy, but before allowing them to enter the portal. This decouples a company engineer with a portal user, as they are not always the same.
It's worth noting that "inactive" in this context doesn't mean a user that used to exist and is now deleted.
One consideration might be to have the following states:
- Active (to represent users who are active and have access to the tool)
- Inactive (to represent users who are not active and don't have access to the tool)
- Not invited (to represent users who are active, but have not been invited to use the tool yet)
Gur Shafriri
complete
Done! you can now create users with a "disabled" status, which will not send an invite and deny them access until invited.
Learn more in the docs
Note - you will need users and teams as blueprints enabled in your organization to use this capability.
Gur Shafriri
in progress
We are now working on the option to create users in Port with "disabled" status, that will give them no access until a decision to invite, so you can depend on the users when building the portal before the launch which