Team access
How colleagues join a project you own, what Read-only and Read-write members can each do, and which actions stay with the owner.
User menu → Access requests
Overview#
A project belongs to the person who created it. Colleagues join it by asking, and you decide whether they can change anything.
When someone at your company starts tracking a domain another colleague already tracks, Seerly tells them the domain is taken rather than building a second, separate project on the same data. They send a request instead, and it lands on your Access requests screen.
Approving a request#
The screen lists everyone waiting, with the address they asked from and the domain they want. Each row carries a role and two buttons.
- Approve adds them to the project with the role selected beside their name.
- Decline dismisses the request. Nothing is shared, and they can ask again later.
The role beside each request is the decision that matters, and it defaults to Read-only.
| Person | Wants access to | Role | Actions |
|---|---|---|---|
| [email protected] | yourcompany.com | Read-only | Approve / Decline |
| Priya Raman · [email protected] | yourcompany.com | Read-write | Approve / Decline |
What each role can do#
Read-only members see everything and change nothing. They can open every dashboard, report and drilldown, filter and export what they see, and set their own notification preferences. What they cannot do is act: no running an analysis, creating or editing content, approving agent output, connecting an integration, or changing project settings. If they try, Seerly refuses the action rather than half-applying it.
Read-only suits the people who read results: a founder who wants the weekly picture, a colleague in another team, an agency contact you would rather not have starting paid runs.
Read-write members work in the project as you do. They can run analyses, create and publish content, approve agent output, and change settings.
What stays with the owner#
Two things never move to a member, whichever role they hold:
- Access requests. Only the owner sees incoming requests for their projects, and only the owner approves them.
- Billing. The plan, payment method and invoices belong to the owner's account.
What to keep in mind#
- The role is per project. Someone read-only on one of your projects is unaffected on any other project they own or belong to.
- Changing your mind means re-approving. There is no role switch on an existing member yet: an owner or an admin has to set the role again.
- A read-only member still receives the project's notifications if they turn them on. Reading is exactly what the role is for.
Next steps#
- Notifications covers what Seerly emails each member about.
- Settings covers the project settings a read-write member can change.