Platform features

Team management

Collaborate with team members and manage access with permission groups.

Why team management?

Invite team members to collaborate on your apps. Put them into groups, like Support or Engineering, and give each group exactly the access it needs.

Use case

A Support group answers tickets for every product without seeing files, variables or app settings.

Permission groups

Navigate to: App → Team → Groups

A group bundles permissions. Everyone in it gets them. Members can be in several groups, and their access is everything their groups give, plus permissions set just for them. Nothing takes access away: to remove a permission, take it out of the group or take the member out of the group.

1
Start
Pick a starting point: Engineering, Support, Support leads, Sales, Viewers, Administrators or a blank group.
2
Details
Name the group, add a short description and an icon.
3
Permissions
Tick what the group may do across the whole app, sorted by area.
4
Products
Optional: access to single products only.
5
Members
Choose who is in the group. You can change it any time.

Inviting team members

Navigate to: App → Team → Invite members

1
People
Enter one or more Vaultix account emails.
2
Groups
Choose the groups they join. Without a group they join without access.
3
Review and send
They receive an email with a link to join. It is valid for 7 days. They get the groups’ access as soon as they accept.

Permission system

Granular control over what team members can do:

Permission	What it allows
Full adminHigh risk	Grants almost all permissions over the app’s content. Cannot open the Team, Settings or Integrations pages (owner only), rename or delete the app, delete products or transfer ownership.
Head supporter	Handles support tickets for every product and manages the ticket archive: opens, searches, archives and restores archived tickets. Only head supporters, full admins and the owner see archived tickets.
Can access all products	View and manage all products instead of just assigned ones.
Can manage all subscriptions	Create, edit, pause, resume, and delete subscriptions for all products.
Can view users	See user list and details (required for most operations).
Can upload/manage files	Upload files to products and delete old files.
Can access support (all products)	Handle support tickets for all products, not just assigned ones.

Product-specific permissions

Groups and members can also get access to single products. Example: a group for one game can:

Allowed

Access support tickets for “Product A”
Create subscriptions for “Product A”
Upload files for “Product A”

Not allowed

Access “Product B”
Change app settings

Effective access

Manage on a member shows three views: their groups, their individual permissions and their effective access, the full list of what they may do with the group each permission comes from.

Managing existing members

Action	Where	Effect
Change groups	App → Team → [member] → Manage → Groups	Takes effect immediately.
Individual permissions	App → Team → [member] → Manage → Individual	Extra permissions for this member only.
Edit a group	App → Team → Groups → Edit	Changes the access of everyone in it.
Remove member	App → Team → [member] → Remove	Immediately revokes all access to the app.

Accepting invitations

From the invitee's perspective:

Receive invitation email with link
Click link to accept invitation (registration is possible via the link)
Review the app name
Accept or reject invitation
If accepted, app appears in the “Collaborating apps” section

Ownership vs. collaboration

	App owner	Collaborator
Origin	Created the app	Invited by owner
Control	Full control over all settings	Limited permissions
Deleting the app	Can delete the app	Cannot delete the app
Membership	Can invite/remove team members	Can leave collaboration anytime
Billing	Pays for storage/resources	No billing responsibility

Best practices

Grant minimum necessary permissions (principle of least privilege)
Give access through groups; keep individual permissions for exceptions
Use product-specific permissions for staff who work on one product
Regularly review team member access (remove inactive members)
Avoid giving “Full admin” unless absolutely necessary
Use activity logs to monitor team member actions

Vaultix · Features · Pricing · Documentation · Changelog · llms.txt