Roles and permissions

Every person in a workspace has one of three roles. A workspace administrator sets the role when inviting someone and can change it later.

Role	In short
Viewer	Can see everything: sources, messages, logs, health, mappings and alerts. Cannot change anything or send anything.
Member	Everything a viewer can do, plus the day-to-day work: test sources, poll now, send test messages, edit and test mappings, promote a tested mapping, and send queued messages again.
Admin	Everything a member can do, plus setting things up: add, change, switch on or off and remove sources, make new webhook keys, manage alert rules, discard queued messages, promote a mapping without a passing test, change and save the orchestration, and manage profiles.

What each role can do, page by page

Page	Viewer	Member	Admin
Sources	See sources, settings and polls	Test connection, poll now, send a test message, add a sample	Add, change, switch on or off, remove, new webhook key
Messages	Read summaries and timelines	Open raw content, send again, run again	Same as member
Queue	See entries	Send again	Discard
Mapping	See fields, versions and releases	Edit, test, promote after a passing test, roll back	Promote without a passing test (recorded)
Field watch	See everything	Check now, re-learn	Same as member
Alerts	See rules and history	See rules and history	Create, change, test and remove rules
Orchestration	See the route and its runs	Same as viewer	Save (loads it into the gateway), check test destinations, run, clear
Profiles	See profiles, versions and where they are used	Same as viewer	Create a profile or a new version
Ask Neev	Ask questions on the Orchestration page	Also build in Projects they can edit	Also have it save the orchestration and load it into the gateway

Some limits apply to everyone

• Nobody can promote a mapping while the go-live check is red. See Mapping.
• Raw message content (the original HL7 or FHIR) is only shown to members and admins, and each time someone opens it, that is recorded in Logs.