Skip to main content
A Stakeholder seat gives someone limited access to Contract Intelligence without using a Legal seat in your organization. Use it for outside counsel, business partners, and other people who should work with selected Vault content but do not need the rest of GC AI.
Your organization may need access to Stakeholder seats and custom roles. Contact your account team if these options do not appear in your settings.

​
How Stakeholder access works

A Stakeholder seat applies only inside the organization that assigned it.
  • It does not consume a Legal seat.
  • It limits the member to permissions that support Stakeholder access.
  • It takes priority inside that organization if the member has a Legal seat through another organization. Their Legal seat remains active elsewhere.
  • If this is the member’s only organization, changing them from your Legal seat to a Stakeholder releases the Legal seat for another member. GC AI keeps the seat assigned when the member belongs to multiple organizations.
Stakeholder access is a ceiling, not a permission grant. The member still needs a role or a direct share before they can access content.

​
Available permissions

Stakeholder seats currently support these Contract Intelligence permissions: Restricted Vault chat can find, filter, compare, summarize, and explain what the admitted documents say. It does not provide legal advice, legal research, drafting, document editing, or access outside the shared Vault content. Permissions for Main Chat, Projects, Tasks, Skills, Playbooks, Automations, Company Profiles, Academy, and the Word add-in do not activate for a Stakeholder seat.

​
How roles affect Stakeholders

Roles define what a member can see and do. A Stakeholder can hold any assigned role, but only the Stakeholder-eligible permissions in that role activate. For example, a role may include Access shared Views, Restricted Vault chat, and Create projects. A Stakeholder receives the first two permissions. Create projects stays inactive because the Stakeholder seat does not support it. Roles granted directly and through user groups combine. Removing a direct role does not remove access inherited through a group.

​
Assign a Stakeholder seat

Organization admins can assign Stakeholder access in several places:
  • Existing member: Open Settings → Organization, select the member’s access badge, and choose Stakeholder seat.
  • Email invitation: Choose Stakeholder seat and the roles the person should receive when they join.
  • Join request: Choose the person’s access and roles before approving the request.
  • Automatic member access: Set the access and roles for future members who join through a shared link, Single Sign-On (SSO), or System for Cross-domain Identity Management (SCIM).
A shared invitation link uses your automatic member access settings. Legal seats require a direct email invitation.

​
Remove a Stakeholder seat

Open Settings → Organization, select the member’s access badge, and choose Remove Stakeholder seat. The member returns to any Legal seat or active trial they still hold. Otherwise, their access becomes View only. If assigning the Stakeholder seat released a Legal seat from your organization, assign that Legal seat again if the member needs it.