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)
Created by Matar Peles
October 2, 2024