One rulebook, for people and AI alike.
Most tools ask you to set permissions once for your team and again for anything automated. Plexvia has one answer: a level is attached to the knowledge or the file, and everyone reading it, person or assistant, stays inside the level they were given.
Four by default. More if you need them.
Everyone, staff and owners cover most of what a small business needs. When they do not, name your own: a finance level, a level for one location, a level for a supplier’s pricing. Levels apply to knowledge and to files, so one change moves everything attached to it.
- Named in the language your business already uses
- Attached to the item, so it travels with it
- Change the level once, and every reader follows
Access levels
Named in your words, set once
- EveryoneAnyone in the business
- StaffPeople on the team
- OwnersYou and your co-owners
- FinanceA level you named yourself
Levels apply to knowledge and files, so one change moves everything attached to it.
The assistant cannot say what you could not read.
This is the part that is easy to get wrong elsewhere. If an assistant reads everything and answers everyone, it becomes a way around your permissions. In Plexvia it reads at the level of the person asking, and in a group thread at the level of the most restricted person in it.
What Sam can see
Front desk
- Opening hours and returnsEveryone
- Trade price listStaff
- Payroll calendarOwners
When Sam asks the assistant a question, it answers inside Sam’s level too.
Three settings that do three different jobs.
A level decides what somebody can see. A role decides what they can change. A permission override handles the one person who is an exception. Custom roles and custom levels are available on the plans that include them.
Levels in your own words
Everyone, staff, owners, or a level you name. Attached to the item, not to a folder.
One boundary, two readers
A person and the assistant helping them answer inside the same level.
Narrowest wins in a group
In a group thread the assistant answers at the level of the most restricted person present.
Roles for what people can change
A role bundles permissions, so a new starter is set up in one action.
Exceptions without new roles
Give one person a little more, or a little less, without inventing a role for them.
Changes are recorded
An audit log covers configuration changes, so a permission change is not invisible.
The rest of the platform
Every part of Plexvia draws on the same knowledge and the same access rules.
Decide who sees what, once.
Set your levels when you set up your knowledge, and everything after that follows them.
Free to start · No card required