> ## Documentation Index
> Fetch the complete documentation index at: https://docs.assuric.com/llms.txt
> Use this file to discover all available pages before exploring further.

# People FAQ

> Quick answers to the things customers ask us most.

<AccordionGroup>
  <Accordion title="What's the difference between a role and a permission?">
    A permission controls what someone can do in the software: Staff portal only, View-only, User or Admin. A role records what they're accountable for, like DPO or Clinical Safety Officer. They're independent, so a person has exactly one permission level and any number of roles. See [Permissions and access](/people/permissions-and-access) and [Roles and groups](/people/roles-and-groups).
  </Accordion>

  <Accordion title="Can staff reach the hazard log or dashboard through the Staff Portal?">
    No. Staff portal only permission has no access to the Assuric dashboard. The portal covers checklists, training, incident reporting and device registration, not the hazard log or anything else in the workspace. See [Manage and customise your staff portal](/people/staff-portal).
  </Accordion>

  <Accordion title="Does adding a training module make it visible to staff straight away?">
    No. A module is invisible until it's attached to a checklist item, on a checklist that's assigned to a group or role and published. Creating the module on its own doesn't put it in front of anyone. See [Assign training through your checklists](/people/training).
  </Accordion>

  <Accordion title="Is Clinical Safety Lead the same as a Clinical Safety Officer?">
    No. Clinical Safety Lead is a coordinator role. It doesn't require clinical registration and can't perform CSO sign-off. If DCB0129 work is waiting on a signature, it's waiting on the CSO. See [Roles and groups](/people/roles-and-groups).
  </Accordion>

  <Accordion title="Can the same person hold both DPO and Data Protection Lead?">
    They can overlap, but shouldn't by default. Once you've appointed both as separate roles, give them to different people, to preserve the DPO's advisory independence. See [Roles and groups](/people/roles-and-groups).
  </Accordion>

  <Accordion title="My own Staff Portal view looks empty. Is the portal broken?">
    Probably not. An admin account's own portal view reflects what's assigned to that account, which is usually little or nothing. Visit it as a staff-permission test account instead of judging it from an admin login. See [Manage and customise your staff portal](/people/staff-portal).
  </Accordion>
</AccordionGroup>

## Related articles

<Columns cols={2}>
  <Card title="People: Overview" icon="users" href="/people/key-capabilities">
    Accounts, groups, roles, checklists and training in one place.
  </Card>

  <Card title="Assigning owners and responsibilities" icon="user-check" href="/people/assigning-owners-and-responsibilities">
    Groups, roles, and how work ends up owned by a team.
  </Card>
</Columns>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.