Invite your event team with the right roles
Invite organisers to a workspace and assign admin, manager, issuer, or support roles so access matches the work each person does.
A single shared login is the default for a small event team, and it becomes a problem the moment someone leaves or a volunteer only needs to check delivery status.
A workspace can have separate members with separate roles.
The roles
Admin manages the workspace, members, billing, and settings. Manager runs certificates, recipients, and forms. Issuer handles issuing and recipient work. Support handles recipient follow-up. The exact boundary matters less than the principle: a support volunteer should not be able to change billing or delete a certificate.
Open Members from the workspace sidebar to invite someone and choose a role. The invitation is tied to the email address; a Google sign-in does not grant access on its own.
Where it helps
A college fest has a core team, a faculty approver, and a group of volunteers handling "where is my certificate?" messages. A training provider has an operations lead, an issuer, and a support inbox. A university department has staff who manage the programme and staff who only need to check records.
What comes later
SSO, SCIM provisioning, and audit logs are separate features for organisations that need identity-provider access control and a reviewable trail. Members and roles are the starting point, not the whole enterprise story.
Related