nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Auto-Assign Users to Groups

zuhair_saadat

Hi all, we rely on Groups to control access and permissions. In our instance, only certain users may approve a workflow, sign an Agreement, or view the Ironclad Repository.

Administering Groups at this time is a manual process, especially since users must first log into Ironclad to activate their licenses.

Idea: Enable IT teams to assign users to Groups when provisioning Ironclad licenses

Has anyone else faced this challenge? If so, how was it addressed in your organization?

Find more posts tagged with

Status: None

Comments

Kshitij_Dua

Hi Zuhar,

We face the same issue. For us, a new user gets either auto assigned an IC account if they are in specific categories, and for others, they have to request IT to get an account. Once, the accounts are created, Legal Ops would assign the individual to various groups. For any automation to make an impact in this, Ironclad would probably need to have their SCIM integration with SSO evolve to have multiple data fields sync into Ironclad.

Best,

Sebastian_Goldsmith

@Kshitij_Dua - out of interest does your IT team therefore have admin level access to Ironclad? One of my main gripes is that for confidentiality purposes I am the only administrator, so I have to be the person adding and removing people from Ironclad.

Kshitij_Dua

Hi Sebastian,

Yes, we have limited people from our IT team as back up administrators to
Ironclad. I agree with your thinking around confidentiality issues, happy
to chat live on how we think about this aspect.

Always my best,
K**bleep**ij

zuhair_saadat

@Sebastian_Goldsmith Agree it would be terrific if there was an admin role which allowed IT to ensure the system/integration is up-and-running but wouldn't give them access to all contracts in the Repository, as is the case today.

@Kshitij_Dua would very much appreciate hearing about your workaround, as currently granting IT an Admin role is non-negotiable--just this week IT helped us resolve an SSO login issue we wouldn't have been able to ID ourselves.

Kshitij_Dua

Hi @zuhair_saadat and @Sebastian_Goldsmith , While I completely agree with the idea of having different admin rights for IT and other business owners in Ironclad, I see this as a larger issue affecting many SAAS solutions that may contain contracts, or part of information from contracts, and may not offer differential admin rights today.

As for our workaround, we don't store some extremely confidential contracts (employment contracts as an example) in Ironclad Repository (yet). For buy and sell side commercial contracts, we believe selected team members of IT who act as back up admins, are included in the "need to know" category to have access to such information.