.5f521cec.png "Trivas.ai")
Give every teammate exactly the access they need.
Trivas lets owners and admins control who can see what, down to the individual page. Start from a role, adjust it per person, restrict invites to your company's email domain, and require two-factor sign-in for everyone in your organization.
Settings pages shown here are available to brand owners and admins. Page-level access is part of the new experience.
Shared data needs more than one door.
An agency analyst should see advertising but not settings. A sales rep does not need supply chain. A new hire should join with the right access from day one. Without per-person control, teams share logins or give everyone everything.
Access is all or nothing
When a tool only has one level of access, the choice is between locking people out and showing them everything.
Anyone with a link can end up inside
Invites to personal or unknown email addresses make it hard to know who is looking at your commerce and ad data.
Agencies juggle many brands
Switching between client workspaces should be quick, while each brand keeps its own sections and settings.
Inside Settings: Team, Company and Security
Everything lives under Settings, grouped by what you are trying to do.
Each tab describes one area of Settings, with its parts numbered.
Manage team members and their permissions from one table, with an invite flow that starts from a role.
Team: members, invites and roles
Manage team members and their permissions from one table, with an invite flow that starts from a role.
- 01
Members table
Each member shows name (or "Pending Invite"), role badge and status, with a search box and a count of active members.
- 02
Edit, Remove and Cancel
Edit a member's access, remove a member, or cancel a pending invitation. Owners and pending invites can't be removed this way.
- 03
Invite Team Member
Enter an Email Address, choose a Role, review the permission checklist and select Send Invitation. The invite stays pending until it is accepted.
- 04
Role defaults
Choosing a role pre-fills the checklist, so common cases take a couple of clicks.
- 05
Per-person overrides
Every box in the checklist can be changed for that person. Saving replaces their whole set of overrides.
What Team and security controls do
Roles and per-person access
Start from a role for the common cases, then adjust any permission for an individual. Each person's access is the combination of their permissions and what the brand has switched on.
Page-level control of the menu
Hide or show individual pages for each person, across Commerce, Advertising, Supply chain and Analytics, including Ad Studio pages such as Budget, Automations, Campaign management and Change history.
Domain-restricted invites
Limit invitations to your company's email domains and set the default role that new members receive.
Organization-wide two-factor sign-in
Add a second step at sign-in for everyone in your organization.
Per-brand sections
Each brand chooses which sections exist, so a brand that only needs Reporting & Analytics can turn the rest off.
Multi-brand switching
Move between brands from the brand switcher in the navigation rail, with a search box when you have many.
Careful store connections
Connect platforms through OAuth. The manual Shopify setup uses read-only scopes only, and you can disconnect integrations from the Integrations page.
Brand theming
Admins can set colours, fonts and corner shape for everyone on the brand in the Design studio.
Who uses it, and for what
Agency lead
Gives an agency analyst access to Advertising but not Settings, and switches between client brands from the navigation rail.
Operations owner
Hides Supply chain from a sales rep with one switch in the page access editor.
IT or security lead
Restricts invites to the company's email domains, sets a default role and turns on two-factor sign-in for the organization.
Finance lead
Lets a finance colleague see Budget and Change history without access to Automations.
What changes for your team
The right access from day one
Roles and a default role for new members mean people join with sensible access, with exceptions handled per person.
Governance without a services engagement
Admins set permissions, page access and security themselves, in Settings.
Built for many brands
Per-brand sections and quick brand switching suit agencies and holding companies running several workspaces.
What it needs, and what it doesn't do
What it needs
- An owner or admin with the team and role permission management access to change who can see what.
- The new experience for per-person page access. The classic layout does not use it.
- A brand admin to change brand sections and the experience switch under Preferences.
What it doesn't do
- The read-only promise applies to your store and retailer data connections. Ad changes are made only in Ad Studio, when it is enabled and you approve them.
- Active sessions management is not yet available.
- A settings audit log is not yet available. Ad Studio has its own change history for ad changes.
Frequently asked questions
Set up access that fits your team.
Book a short walkthrough and we will show roles, page access and security settings on your workspace.