Migrate users to Azure AD - Expiry
Hi, We are starting to move our users from password/recovery kit to Azure AD integrated. This has been going fine and we started by using a AD security group to provide the access. We had planned to use this group moving forward as we roll people onto the Azure AD SSO/SCIM, but it appears that the migration expiry date of the group is a fixed date from when the group was added. I would like not to have to create a new group as I migrate users, but I also don't want to move them all in a hail-mary fashion and add them all to the group now. Is there any way to change the migration expiration date? It appears that I can only set the maximum time as 30 days. I'm also afraid to remove the group and re-add this as it might invalidate the users who are already using the Azure SSO. Thanks for any information Jonathon Page10Views0likes1CommentAssign permission to access on item level
Our team uses 1Password, and as we've grown, managing password access has become a significant challenge. Currently, to give specific people access to an item, we have to create a new vault. Since an item can only be in one vault, we end of creating many vaults to manage permissions. This means that every time we need to grant access to an item, we have to update multiple vaults and user permissions, which is time-consuming and error-prone. This has made our permission management very complex. Is there a more efficient way to grant item-level permissions or a better workflow to manage access for a growing team without creating a new vault for every single use case? edit: we are currently on the team plan22Views0likes1Comment