What each team role can see and do inside a project

Instead of making you tick dozens of technical checkboxes every time you invite someone, véltica organizes permissions into clear, self-contained roles built around what each person actually does in your business. That prevents common mistakes—like giving someone access to orders while forgetting to give them access to the customer details behind those orders.

Summary of available roles: Owner, Administrator, Editor, Design, Content, Finance, and Read-only

When you invite someone from Team (or check the Role reference card), you’ll see the access levels ordered from broadest to narrowest scope:

Dashboard role	Who it’s built for	What they can do in the project
Owner	The account holder who owns the project.	Full control over the project, its billing, deleting the site, or transferring it to another account.
Administrator (Admin)	Business partner or general manager.	Everything in the project: edit the site, manage the catalogue, payments, Stripe, domains, integrations (Omnisend), restore backups, and invite or remove members in Team.
Editor	Day-to-day website manager.	Edits the site, pages, blog, CMS collections, forms, contacts, bookings, traffic analytics, and site Settings (including policies), with no access to finances (no payments, payouts, or Stripe account).
Design	Web designer or creative agency.	Works in Pages, the visual Editor, the Images/Files library, the AI assistant, and visit analytics. Can read the CMS to lay out pages, but cannot touch contacts, bookings, or money.
Content	Copywriter, social media manager, or support lead.	Manages Blog, Content (CMS), Forms, Contacts, and images/files, and can use AI. Views pages in read-only mode without altering site settings or sales.
Finance	Store manager, cashier, shipping lead, or front desk.	Manages Catalogue / All offers, Payments, Coupons, Shipping, Payouts, Stripe, Bookings / Appointments, and all Analytics (visits, sales, and bookings), plus viewing Contacts. Does not edit site design.
Read-only (Viewer)	External consultant, auditor, or reviewing partner.	Sees everything and changes nothing: can view pages, CMS, forms, contacts, appointments, payments, analytics, and backups in read-only mode.

Every working role (Owner, Administrator, Editor, Design, Content, and Finance) can also post in the shared Team notes log on the Home screen.

Which menu sections each role sees (why unauthorized sections are hidden from the sidebar)

In véltica, the dashboard sidebar and the server read the exact same permissions table. When a collaborator opens your project, sections their role isn’t allowed to open don’t even appear in their sidebar:

• Someone with the Design role enters the project and sees a clean menu focused on Home, Website → Pages, Analytics → Visits, and the button to open the Editor; they won’t see Sales, Catalogue, or Settings folders that would throw an error if clicked.
• Someone with the Finance role sees the entire commercial suite (Catalogue, Sales, Bookings, Analytics, and Contacts), without technical settings or marketing integrations getting in the way.

Before sending any invitation in Team, you can expand each role’s details to see in two clear columns which sections it Includes and which it Does not include.

Which actions belong exclusively to the Owner (deleting the project, transferring ownership, and managing the plan)

Even though an Administrator can run almost the entire day-to-day operation of the site and team, three keys never leave the hands of the project Owner:

1. Deleting the project (Settings → Site settings → Delete project).
2. Transferring the site to another account (Settings → Transfer site).
3. Managing the membership, payment cards, and billing usage (User menu → Plans / Billing and Settings → Usage and limits).

This lets you delegate full administration of your store or website knowing that no collaborator—not even an Administrator—can delete your business or transfer project ownership away.

How to change a team member’s role at any time

If someone’s responsibilities change in your business (for example, the person who helped only with Design is now also going to run Content or manage the whole site as an Editor), you don’t need to remove and re-invite them:

1. Open Team from the project sidebar.
2. In the Members with access list, find the person.
3. Open their Role selector and pick the new role.

The change takes effect immediately: the next time they switch screens or reload the dashboard, their sidebar and editor permissions adjust automatically to the new role.