User Management

Organizations

Every owntag account belongs to at least one organization. Organizations are the central unit for managing setups, team access, and billing. When you sign up, a default organization is created for you automatically.

All setups belong to an organization. Every member of that organization can access all of its setups. This means you only manage access once at the organization level — no need to invite colleagues to each setup individually.

You can create additional organizations at any time, for example to separate different clients, business units, or projects.

Roles

Each organization member has one of three roles: Owner, Admin, or Member. The table below shows what each role can do.

Multiple owners

An organization can have more than one owner. This prevents a single point of failure — if one owner is unavailable, another can still manage the organization fully. Any owner can promote a member or admin to owner, and any owner can demote another owner to admin (as long as at least one owner remains).

Inviting members

To add someone to your organization, go to Organization Settings → Members and enter their email address. The person you are inviting must already have an owntag account. If no account is found for the email, you will see a message with a link to share so they can sign up first.

Once added, new members immediately have access to all setups in the organization. There is no accept/decline step — access is granted right away.

Collaborators vs. members

Not everyone who needs access to a setup should be a full organization member. owntag distinguishes between two types of access:

• Members belong to the organization and can see all its setups. Membership is managed at the organization level.
• Collaborators are external users (freelancers, consultants, partners) who get access to specific setups only. They do not see the organization’s other setups or settings.

Collaborator permissions

By default, collaborators have read-only access. They can view everything about a setup — overview, statistics, domains, features — but cannot change anything. All form inputs and action buttons are visually disabled, and a notice at the top confirms their read-only status.

If a collaborator needs to make changes, an admin or owner can grant them write access on a per-setup basis. Write-access collaborators can interact with the setup just like an organization member, except they cannot delete the setup.

Managing collaborators

There are two ways to manage collaborators:

• Per setup: In a setup’s settings, add a collaborator to that specific setup. This is the simplest approach when granting access to a single setup.
• Organization-wide view: In Organization Settings → Collaborators, you can see all collaborators across all setups at a glance. From here, you can add a collaborator and select which setups they should have access to, or adjust an existing collaborator’s setup assignments in bulk.

Only admins and owners can add or remove collaborators. Members can see the collaborator list but cannot modify it.