Team management & RBAC

Find your organisation’s members

Open Organizations, select the organisation, then use its Members tab to review membership and invitations. Choose Invite member and enter the person’s email address. They receive an invitation link. The invite form lets you assign an organisation role; you can change the role later from the same members area. Menu items and actions depend on your permissions.

Roles

DNS by echo reply ships six role presets. They are starting points; an organisation administrator can adjust a preset or create a custom role. Use the permission summary in the current role editor as the source of truth: the available controls can include feature-specific access such as supplier evidence, and may change as the application adds features.

The presets cover common jobs:

  • Admin — broad organisation administration and role management.
  • Technology — DNS, templates, registrations, and compliance work.
  • Viewer — read-only access to common DNS and registration information.
  • Billing — billing and subscription work, with registration visibility.
  • Record Manager — manage records without managing zones or billing.
  • Registration Manager — register, renew, and transfer domains without access to DNS records or billing.

Each organisation also has an owner role. It always has role-management rights and cannot be deleted while it owns the organisation. Only the owner can transfer ownership.

Transfer organisation ownership

Only the current owner can start a transfer. Use this when responsibility for the organisation is changing; it does not move domains, DNS zones, or billing to another organisation.

  1. Open Organizations, select the organisation, and choose Transfer Ownership from its details or settings.
  2. Select an existing organisation administrator as the new owner.
  3. Enter the reason for the transfer. The form requires at least 10 characters.
  4. Type the organisation name exactly as shown to confirm, then submit.

The application changes the owner and records the transfer in the organisation’s ownership history. The history shows previous owners, dates, and the recorded reason. Open Ownership History from the organisation’s details to review it. If you are not the current owner, ask them to make the transfer.

The role editor separates view and edit access for areas such as DNS, billing, registrations, and compliance. It also has controls for incident reporting, change approval, and self-approval. Review each setting before saving instead of assuming a preset includes every permission your team needs.

Risk-assessment sign-off is a separate named-person grant. It is not implied by Admin, role-management, or compliance access.

Self-approve changes bypasses the pending-change review step for that person’s own changes. Treat it as organisation policy and grant it deliberately.

Custom roles

Users with Manage roles can create and edit roles. Role changes apply immediately and do not use the DNS pending-change approval flow. Review the permission summary before saving: a custom role can combine access in ways the presets do not. For example, a billing user does not need record access, and a record manager does not need billing access.

Management history and exports

Supported management changes are written to append-protected history and shown in tenant-scoped activity and object-history views. Entries identify the time, acting user, action and available before/after details.

CSV export is available for supported object-history views. Enterprise organisation administrators can also generate compliance-report exports in PDF or CSV from the compliance area. Export availability therefore depends on the view, role and plan. It is not a promise that every event can be downloaded from one screen.

echo reply does not currently publish a customer-facing retention duration for this history. Do not rely on this guide as a records-retention schedule. Align required archival with your organisation’s policy and contract.

These controls can support evidence collection, but using them does not by itself establish compliance. See the security and regulatory controls guide.