Roles and permissions - Dapping Docs

Roles decide which identity you act as and which actions you can take. A company role, a public team listing, a verified experience, and a project team credit are four separate relationships. None of them implies another.

Company roles

A company hub has three roles: Owner, Admin, and Member.

Action	Owner	Admin	Member
Publish listings under the company	Yes	Yes	No
Invite a teammate	Yes	Yes	No
Change a teammate’s role	Yes	Can only promote a member to admin	No
Remove a teammate	Yes	Cannot remove another admin	No
Transfer ownership	Yes	No	No

Invitations name the person by email address, wallet address, or @username, and can be sent as admin or as member. Nobody can be invited as owner.

One owner, always

A company hub has exactly one owner, and the owner cannot be removed or demoted. Making someone else the owner is a transfer, and the target must already be an admin, so promote them first. After a transfer the previous owner becomes an admin. There is no limit on admins.

Removing a teammate

Removing someone ends their current listing on the company’s People tab. It does not erase a verified experience they already hold. Public professional proof and workspace access are reviewed separately.

Project teams

A project team carries two independent things. Team credit is the public claim. It is requested or offered and becomes public only once the other person accepts, sitting at Pending until it is Approved or Rejected. It says nothing about who may edit the listing. A team role is the private permission: Owner, Admin, Editor, or Viewer, starting at Viewer.

Action	Project published from a company hub	Project published from a proof page
Edit the listing	Company owners and admins	The creator, or a team Owner, Admin, or Editor
Add or remove team members	Company owners and admins	The creator, or a team Owner or Admin
Delete the listing	Company owners and admins	The creator only

Members can also state what they contributed, such as engineering, design, or research. Contribution is self-declared, grants nothing, and stays separate from the role above, so nobody gains edit rights from a job title.

Group conversations

Group conversations have three roles: Owner, Admin, and Member.

Action	Owner	Admin	Member
Send messages	Yes	Yes	Yes
Add members	Yes	Yes	No
Manage the invite link	Yes	Yes	No
Edit group settings	Yes	Yes	No
Remove a member	Yes	Members only	No
Promote or demote an admin	Yes	No	No
Transfer ownership	Yes	No	No
Delete the group	Yes	No	No
Leave the group	Transfer ownership first	Yes	Yes

Publishing context

A listing names one accountable publisher: the signed-in builder, or the company, published by one of its owners or admins acting as that company.

Safe role management

Grant the least access the person’s work needs, and review it when responsibilities change. Workspace access and public professional proof are separate records; read them separately.

Manage company roles, invitations, and ownership

Invite teammates, review access, and transfer ownership safely.

Understand company-listed roles and verified experience

Separate workspace access from public professional proof.

​Company roles

​One owner, always

​Removing a teammate

​Project teams

​Group conversations

​Publishing context

​Safe role management

​Related guides