Docs
Roles, approvals and access
Roles and permissions in a Signal over Noise workspace, how changes to your tools are approved, what the audit log records, and how to export or erase your data.Read this page as MarkdownWho can see and change what in a Signal over Noise workspace, how a change to one of your tools is approved, and what the workspace records. Where your data is hosted, who processes it and how long it is kept are set out in our Privacy Notice and your data processing agreement with us; this page does not restate them.
Roles
Everyone in a workspace has one of three roles. Admins run the workspace. Members use it day to day. Collaborators are people from outside the company, such as an agency, who work on creative and artifacts. Because they are external, collaborators cannot see company objectives or company context at all, whatever else their role allows.
| What a person can do | Admin | Member | Collaborator |
|---|---|---|---|
| Open the workspace and read its pages | Yes | Yes | Yes |
| Read Pulse | Yes | Yes | — |
| Ask questions and keep conversations * | Yes | Yes | Yes |
| Create and edit artifacts and dashboards * | Yes | Yes | Yes |
| Draft ads and creative in Ask * | Yes | Yes | Yes |
| Run automations, and approve or reject changes * | Yes | Yes | — |
| Connect and manage integrations * | Yes | — | — |
| Change workspace settings and export its data | Yes | — | — |
| Set the AI policy | Yes | — | — |
| Invite and manage members | Yes | — | — |
| Read the audit log | Yes | — | — |
* Needs a paid plan as well as the role.
An admin changes someone’s role in Settings → Members & roles. Objectives and company context are written by admins only; see Company objectives and Company context.
Approvals
Signal over Noise reads your tools, but a change to one waits for a person. When it proposes a change, such as pausing an ad set or drafting new ads, it opens an approval that shows the exact change, field by field, as it is now and as it will be after approval. Approving lets it carry out exactly what is shown and nothing else; rejecting changes nothing. Drafts it prepares for an ad platform are created there as drafts, for your team to publish.
Anyone whose role can run automations can approve or reject a change: by default, admins and members. Ad drafts need a second person: whoever asked for them can reject them but not approve them, unless they are an admin, and an admin approving their own request is recorded as such.
AI clients
People in a workspace can connect their own AI assistant, which works as them with their role. How it connects, what it can do and how its proposals are approved is on Connect your AI client.
Audit log
The workspace records who did what and when: tools connected and disconnected, approvals and the changes they carried out, changes to objectives, company context, members, roles and settings, and data exports and erasure. Admins can read the most recent events in Settings → Audit.
Exporting and erasing your data
An admin can export the whole workspace as a file from Settings → Data & retention. From the same place an admin can erase the workspace and its data: it starts as soon as they confirm by typing the workspace’s address, and it cannot be undone. What erasure covers and how long it takes are set out in your agreement with us.