Team administration

Assign a role to a team member

Use this page to give someone access to a role in a ResearchOps team you manage.

If the person is not already an active member of the team, ResearchOps will add them when you assign the role.

Only assign the lowest role they need to do their work. Role changes and team creation are recorded in the audit log.

Sourcebook gate

Sourcebook gate for role assignment

Evidence needed

Do not assign role permissions until the Sourcebook clause and required access evidence are in place.

Add evidence before continuing

  • Sourcebook context Matched 1 clause matched this route.
  • Evidence readiness Evidence needed 2 evidence items needed.
  • Governance action Pause for evidence Add the required evidence before treating this workflow as Sourcebook-ready.

Evidence ledger

Evidence ledger for role assignment

Track the evidence needed before role permissions or admin access are assigned, changed or reviewed.

Evidence ledger for role assignment
Evidence Sourcebook clause Status
Access Request access-request Needed
Role Permission Model role-permission-model Needed

Team scope

Checking which team you can manage.

Role assignment details

1. Team member

Use the email address they use to sign in.
Use a user ID instead

Only use this if you copied the user ID from ResearchOps. If you enter both an email address and a user ID, they must belong to the same person.

2. Team

Which team should this role be in?
Choose an existing team, or create a new team before assigning this role.
You will become Team Admin for the new team.
Select a team
The person will be added to this team if they are not already a member.

Loading teams you can manage.

3. Role

What role do they need?
Start with the lowest role that gives the person what they need.
Can observe low-risk research context without seeing participant personal data.
Can create and update governed research records.
Can create, update and review governed research records.
Can review and approve governed research records.
Can view, record, resolve and audit safeguarding concerns.
Can manage team membership, role assignment and general audit oversight.

4. Access duration

How long should this role last?
Choose a governed access period. The standard maximum is 180 days.
Use for short support tasks or temporary cover.
Use for short project involvement.
Use for one research phase or delivery cycle.
Use for the standard maximum team access period.
Use for contractors, secondments or known assignment end dates.

5. Reason

This will be stored in the audit log. Include the work they need the role for. For example, "Joining the research team for the May assisted digital study".