Organisation
Manage your team, roles, and organisation settings.
DNS Watchdog uses organisations to group users and isolate data. All DNS providers, zones, records, and issues belong to an organisation — team members within the same organisation share access to the same data.
Personal workspace vs organisation
When you first sign up, you start in a personal workspace. You can:
- Stay personal — use DNS Watchdog as a single user
- Create an organisation — invite team members and collaborate
To create an organisation, go to Settings → Organisation and click Create Organisation.
Roles
Every member of an organisation has one of five roles:
| Role | Summary |
|---|---|
| Admin | Full access — everything a Member can do, plus manage providers, members, and billing |
| Member | Day-to-day operations — act on findings, but cannot change providers, members, or billing |
| Read-only | View and export everything; cannot make any changes |
| Brand Protection | Brand Protection only — triage copycat domains and raise Jira tickets for them; sees nothing else |
| Brand Manager | The domain cleanup review only — an external brand manager who says which of their brand's domains to keep or release; sees nothing else |
What each role covers
Admin has full control of the organisation:
- Everything a Member can do (below)
- Connect, update, and remove DNS providers, and trigger provider syncs
- Manage billing and the subscription
- Invite and remove members, and change member roles
- Manage organisation settings
Member covers the day-to-day security workflow:
- View all zones, records, IP addresses, issues, certificates, screenshots, and change history
- Trigger rescans of zones, records, and DNS redirects
- Ignore and restore issues; ignore and unignore certificates
- Manage ignored IPs
- Add and edit notes
- Run deliverability tests
- Manage notification channels and preferences
Members cannot change which DNS providers are monitored, manage billing, or manage the organisation's membership.
Read-only is for stakeholders who need visibility without the ability to change anything — auditors, executives, or adjacent teams:
- View all zones, records, IP addresses, issues, certificates, screenshots, and change history
- Export data
Read-only users cannot trigger scans, modify issues, or change any settings.
Brand Protection is for a brand or legal team that works copycat domains and nothing else. The product narrows to Brand Protection: it is the only entry in the sidebar (alongside their own profile and help), every other page redirects there, and the API refuses the role outside it. Within Brand Protection they hold a Member's powers — triage findings, export them, and raise Jira tickets for them. See Roles and access for the full capability table.
Brand Manager is for the person outside your DNS team who decides what a brand registers. You do not invite them by hand: sending a domain cleanup request invites the brand's manager with this role and emails them a link that signs them up and opens their review. The product narrows to that review (plus their own profile): every other page redirects there and the API refuses the role outside it. Within the review they keep or release each of their brand's domains and finish it; they see no other brand and nothing else in your estate.
Managing members
Admins can invite new members, remove existing members, and change roles from the Organisation settings page.
To invite a team member:
- Go to Settings → Organisation
- Click Invite Member
- Enter their email address
- Select a role (Admin, Member, Read-only, or Brand Protection) — Member is the default. Brand Managers are invited by sending a domain cleanup request, not from here
- Click Send Invitation
The invited user receives an email with a link to join your organisation.
Switching organisations
If you belong to multiple organisations, use the organisation switcher in the sidebar to switch between them. Each organisation has its own isolated set of providers, zones, records, and issues.
Admin access required
Creating, updating, and managing organisation settings requires the Admin role. Users with the Member or Read-only role who need elevated access should contact an existing admin.