Roles & Permissions in GIRI

🔐 ADMINISTRATION

Roles & Permissions in GIRI

Eight team roles control who can create, approve, and manage instructions — from read-only viewer to team admin.

📌 The core principle: roles apply per team

Every role is assigned per team — the same person can be an Editor in team A and just a Viewer in team B. One exception: Org Admins (organization level) automatically hold Team Admin rights in every team of their organization.

The 8 roles at a glance

👀 Viewer Read-only

Consumes approved instructions in the app — the default role for everyone on the shop floor. Cannot change anything.

View instructions

✏️ Editor Content author

Creates, edits, and deletes instructions — but cannot approve. The role for everyone producing content.

View instructions Create instructions Edit instructions Delete instructions

✅ Approver Quality gatekeeper

Grants both approvals (technical + data privacy), locks instructions, and manages web links. Does not author content — the compact reviewer role for smaller teams.

View instructions Technical approval Data privacy approval (GDPR) Lock instructions Manage web links

🔧 Technical Approver Technical gatekeeper

Reviews technical correctness: technical approval, locking instructions, and managing web links.

View instructions Lock instructions Technical approval Manage web links

🛡️ Compliance Approver Privacy gatekeeper

Reviews the data-privacy side: GDPR approval, locking instructions, and managing web links.

View instructions Lock instructions Data privacy approval (GDPR) Manage web links

🗂️ Compliance Manager Access & privacy

Manages team users and grants the GDPR approval; also locks instructions and manages web links. Does not author content.

View instructions Lock instructions Manage web links Data privacy approval (GDPR) Manage team users

Note: When managing users, can only assign the Viewer and Compliance Manager roles.

🛠️ Creator Full lifecycle

The union of Editor and Approver: creates, edits, deletes — and pushes instructions through all quality gates (both approvals, locking, web links). Also manages projects.

View instructions Create instructions Edit instructions Delete instructions Technical approval Data privacy approval (GDPR) Lock instructions Manage web links Manage projects

👑 Team Admin Full authority

All rights in the team: the full lifecycle plus user and project management, team settings, and all analytics.

View instructions Create instructions Edit instructions Delete instructions Technical approval Data privacy approval (GDPR) Lock instructions Manage web links Edit team details Manage team users Manage projects View analytics Job-done statistics

Which role for whom?

💡 Rule of thumb

Operators → Viewer · Everyone producing content → Editor · Quality → Approver (small teams) or separate Technical + Compliance Approvers (larger orgs) · Process owners with full lifecycle → Creator · Privacy & access management → Compliance Manager · Team leads → Team Admin. Principle: as few rights as possible, as many as needed — upgrading later is always possible.

Good to know

⚠️ Common misunderstandings

Editors author but cannot approve — approvals live with the approver roles. Anyone needing both gets Creator. Approver roles do not author content — reviewing and producing stay separable. Roles are team-scoped: joining a second team means starting with the role assigned there. Analytics and team settings are Team Admin only.

Related articles
ISO 27001: Information Security at GIRI → Server & Hosting Options

Roles & Permissions in GIRI

Who can do what — the 8 team roles at a glance.