Guides by role
Contributor guide
Do your part: the controls and tests assigned to you, the evidence to provide, and nothing else to learn.
Role: Contributor You act on what is assigned to you, not on a whole domain. The role gives no right at domain level: it applies to the controls and tests assigned to you.
Your typical week
- Open My work: the items that fall to you (today, the external auditor's requests and the vendors you own).
- For a control assigned to you, open Controls: the state, expected evidence, tests, and the risks that rely on it.
- Add the requested evidence: Evidence (a file, a link or a frozen Jira query).
- If a test is yours, read its result in Tests and continuous monitoring.
Screenshot to come
Good evidence
- It is dated and recent: evidence older than its frequency is "stale" and no longer counts.
- It says what it shows: a clear name and a type ("Document", "Link", "Screenshot", "Report", "Attestation", "Ticket").
- It holds no unnecessary personal data.
What you may not see
A contributor alone does not read other domains. If a screen is closed to you, that is expected: ask the administrator for read access (the Reader role); roles are additive. If the installation's "Default access" is "Reader" (the starting choice), you already read most registers without another role; if it is "Contributor", you see only what is assigned to you.
What the app does not do
- It e-mails you only if the compliance manager turned reminders on, and only for a task whose Jira ticket is assigned to you.
- It does not read your files and does not check that an address answers: it only checks the
https://format. - It does not remove evidence once added.
Was this page helpful?