Companies and roles
How a tenant, its companies, users, roles and permissions fit together, and how every change is recorded.
Access in Tosven is decided per company and checked every time data is read. This page explains the structure: the tenant and its companies, how a person gets rights, what the built-in roles are, and what the audit trail keeps.
Tenant and companies
Your organisation has one tenant. Inside it you keep one or more companies. Each company is a legal entity with its own country, business id, base currency and books.
Kaarna Group runs three companies in one tenant: Kaarna Group Oy in Helsinki, Kaarna Services Oy in Espoo and Kaarna Sverige AB in Stockholm.
- Books are per company. A journal entry, an invoice and a bank account always belong to exactly one company.
- Nothing crosses tenants. No figure, search result or list ever combines data from two tenants.
- Group views respect rights. A board that shows all companies shows each one only to readers with rights in that company.
Users and memberships
A user is a person with a sign-in. The user account itself carries no rights. Rights come from a membership, which connects the user to a tenant.
There are three kinds of membership.
| Membership | Who it is for |
|---|---|
| Member | Your own staff |
| Accountant | An external accountant working in your tenant |
| Portal | A customer contact, limited to one customer's own records |
Each kind has a ceiling that no role can exceed. A portal membership stays narrow whatever role is attached to it.
An external accountant who serves many clients has a separate membership in each client's tenant. Each client manages only its own.
Roles, per company
A role is a named bundle of permissions. Tosven has six built-in roles: owner, admin, approver, member, viewer and external.
A role is granted for one company, or for all companies in the tenant. Elina Koskinen can be an approver in Kaarna Group Oy and a viewer in Kaarna Sverige AB. Her role in one company gives her nothing in the other.
A few rules apply to every grant.
- Default is no access. Rights are only added. There is no hidden default that opens a module.
- You can only give what you hold. A person grants a role only in companies where they hold every permission in that role. Only an owner can make another owner.
- The last owner stays. The last active owner of a tenant cannot be suspended or lose the owner role.
- Managing members is its own right. Inviting or deactivating people does not bring any business permission with it.
Permissions
A permission is one specific right, such as reading ledger figures, posting a voucher, approving a voucher or reading salary fields. Roles are built from permissions, and every check runs on the permission itself.
Sensitive data has its own permission. Reading a restricted field needs that right explicitly, and so does a total computed from it.
What you see follows from your permissions everywhere.
- A figure you may not read shows as no access. It never shows as zero.
- A record card in a message shows only the kind of record if you lack the right to read it.
- A person may be allowed to decide a card without being allowed to read the figures on a board.
The ledger is never shared record by record. It is visible per company or not at all. Customer records, wiki pages and conversations can be shared more finely.
Agents inside the same rules
An agent is granted rights per company and per module, with an autonomy ceiling and an expiry date. Its effective rights are the overlap of its own grant and its manager's current rights.
If the manager loses a permission, the agent loses it at the same moment. An agent without an active human manager is suspended.
The audit trail
Every change to access is appended to a log. Nothing in it is edited or removed.
- Grant history. Each grant and withdrawal is stored with who made it, when, and under which right. You can ask what a person was allowed to do on any past date.
- Decision log. Privileged actions record which grants allowed them. Privileged reads, such as salary data or an analytics export, are logged too.
- Signed work. Proposer, decider and executor of an agent's work are three separate entries.
On the way
A settings screen for members, roles per company and delegation, with an inspector that explains why a person can or cannot see something, is planned. Two-step sign-in and a free seat for external accountants with a list of all their clients are also on the way. In the pilot, access is set up together with the Tosven team.
Next steps
- Core concepts: tenant, company, role and agent in one place.
- Security and data: backups, where data lives and erasure.
- Agents: how an agent's manager and autonomy level limit what it can do.