FAQs
/
General

How are project permissions restricted by role and organisation?

SYMPRO AI uses organisation-level separation and role-based access controls. Users should only access projects, modules, and administrative functions that belong to their organisation and match their assigned role.

What this means in practice

  1. Organisation separation: project data is scoped to the relevant company, university, or organisation account.
  2. Role-based controls: admin, editor, reviewer, analyst, and other permissions restrict what a user can view or change.
  3. Project assignment: reviewers and analysts generally work only on assigned projects or tasks.
  4. Administrative access: project setup, user management, publishing, and platform-level controls are limited to authorised users.

This matters because review projects can contain unpublished protocols, licensed documents, confidential client work, and internal decisions.

Back to FAQ ListHave more questions? Submit a request
More in General
Are credits shared between team members?
Can data, references, and documents move between SYMPRO AI tools?
Can organisations purchase additional credits, and what happens when credits run out?
Does SYMPRO AI track project activities and decisions by user?
How do AI credits work, and which actions consume credits?
How does human-in-the-loop review work in SYMPRO AI?
Is customer data used to train SYMPRO AI models?
What is included in the SYMPRO AI free trial?
What privacy and quality credentials support SYMPRO AI?
Where can users find training, user guides, technical support, and bug reporting?