AuraDoc
Sign inSign up

Blog

Team roles and permissions in AuraDoc

Invite colleagues, give each person the right role and keep sensitive actions limited, with invitations you can resend, revoke and review.


A document workspace is only useful if the right people can reach it and the wrong people cannot. AuraDoc handles this with roles. Every person in your workspace has one, and the role decides what they can see, change, delete or manage. This article explains the roles, how invitations work and where to look when you want to review who has access to what.

The roles

Four roles can be chosen when you invite someone: viewer, member, editor and admin. Viewers can read documents and workspaces, search, chat with the documents they can see, look at analytics and browse connected cloud storage, but they cannot change anything. Members can also create and update documents, use the AI features and request signatures. Editors have everything members have, plus the ability to delete documents and to create and change workspaces. Admins hold every permission in the workspace, including managing people, settings, workflows and integrations. The owner is the person who created the account and keeps full control.

Two details are worth knowing. A member who uploaded a document can still delete that document, even though members cannot delete files uploaded by others. And when a script or an integration talks to AuraDoc through an API key, the key never widens access: the permissions it can use are the ones shared by the person's role and the scopes selected for that key. You can read more about keys in webhooks and the REST API.

Inviting people

Open Dashboard › Settings › Team to invite a colleague by email and choose their role. The invitation expires after seven days by default. You can set a different lifetime, from a few hours up to a year, or let it never expire. When you are onboarding a whole department, you do not need to type addresses one by one: the bulk invitation dialog accepts a list or a file and sends up to 50 invitations at once, showing a preview so mistakes are caught before anything is sent.

Invitations are not fire and forget. Pending ones can be resent if the email got lost and revoked if you changed your mind or invited the wrong address. A history of invitation activity is kept in the same page, so an administrator can see who invited whom and when. Only people with the permission to manage users can do any of this, which is why a viewer or an editor never sees the invitation controls.

Seats, access and review

Each plan includes a number of team seats, and the Team page shows how many are in use. People you remove stop counting against the limit, so a seat is freed as soon as someone leaves. If your team outgrows the plan, the pricing page lists what each plan includes. Single sign-on and automatic user provisioning are available on the Enterprise plan only; if you need them, contact us.

A good habit is to give people the lowest role that lets them do their job, and to look at the Team page once in a while. Promote someone to editor when they need to delete or reorganise, keep admin for the few people who manage settings, and remove access the same day someone leaves. Role-based access is one piece of a wider approach to protecting documents, described in privacy and compliance built in. Colleagues can also be mentioned by name in the collaborative editor, and the list of people comes from the same team page.

Back to the blog