Team roles and permissions
The five roles from viewer to owner, what each one can reach, and how to invite someone to help.
Each website has its own team, and each person on it holds one role — yours can be different on two different websites. Five built-in roles come with every website, from viewer to owner, and each can do everything the one before it can. On plans that include them you can also build roles of your own (see below).
| Role | Can |
|---|---|
| Viewer | Look around the dashboard. Can't change anything. |
| Author | Write their own posts and pages, as drafts. Can't publish. |
| Editor | Publish, and edit or delete anyone's content. |
| Admin | Manage the team, domains and settings. |
| Owner | Everything, including billing and deleting the website. |
One rule protects the person at the top: an admin can manage the rest of the team, but can never change or remove an owner. Otherwise a weaker role could quietly take over a website from a stronger one.
Custom roles
When none of the five fits — someone who runs the shop but shouldn't touch the blog, or a writer whose posts an editor publishes — build a role of your own under Users → Roles. Tick what it may do in each section: view, create, edit, publish, delete, change the section's settings, or export. In posts, appointments, the calendar and grading you also choose whether that covers only the member's own work or everyone's — in grading, the member's own work means the courses they tutor.
- Start from scratch, or duplicate a built-in role and adjust it.
- You can only give permissions you have yourself, and you can't change or delete a role that has more than you.
- Changing a role changes it for everyone who holds it, straight away.
- A role people still hold can't be deleted — give them another role first.
- Billing and deleting the website are never part of a custom role; they stay with owners.
Seeing who changed what
Admins and owners can open Activity to see the changes the team has made in the dashboard — publishing and deleting, design and settings, domains, members, billing, API keys — each with who made it and when, newest first. Filter it by person or by kind of change. A year of history is kept.
People who sign in on your site
Your team runs the website. The people who sign in on the site itself — learners, members, customers — are a separate list, under Users → Site accounts: each with their email and name, when they joined, when they last signed in and the courses they're enrolled in. Search by email or name, or press Export to Excel. Anyone whose role can see the team can see this list. How they sign in is under Users → Sign-in; see How members sign in to your site.
This is separate from running VPress itself
Your role above is per website. Whether someone operates VPress as a platform is a completely different thing that has nothing to do with any website's team, and the two are never mixed up in the dashboard.
Adding someone
Under Users, type the email address of someone who already has a VPress account and choose the role you want them to have. They're added straight away — there's no separate invitation to accept. If they don't have an account yet, ask them to sign up first.
Whether the Users section itself is available, and how many teammates you can add, depends on your plan.
Still need help?
If the articles don't answer your question, open a ticket and the VPress team will get back to you.