Companies, roles and support access
Each company sees only its own data, and support access stays in plain sight
One system serves several companies. The rules about who sees what run in the database, not only on screen, and when someone from support steps in to help, it is written down.
The problem
Whoever runs your software can usually see everything, and you never find out
Many tools separate customers only on screen. If a direct query reaches the database, the separation is gone. And when support looks into a problem, nobody asks for a reason or keeps a record.
In a construction company not everyone should see everything: the site engineer on one project does not need another project's payment claims or its staff. A role permission that ignores the project falls short.
How it works
Four rules, applied where they cannot be skipped
One space per company
Each company has its own space, with its data kept apart in the database. If a company is suspended, dropped or archived, it loses access right there, and its client portal closes.
Role and project where money and staff are involved
For payment claims, invoices, staff records, filed payments and cash, reading requires a seat on that record's project. Writing also requires the company contract and the module active on that project. Marking invoices as paid, deleting and moving cash stay with the owner or an admin.
Support with a reason and a clock
Support staff enter a company only with a written reason of at least 10 characters. The session lasts 2 hours and whoever enters sees a fixed notice that they are acting as that company. Without a session, they see only the profile card and the counters. A closed company cannot be opened.
A log the company reads
What happens during the session goes into a log that cannot be edited or deleted. The owner or an admin reads it in Settings, with the reason and how the session ended: exit, replaced, expired or company closed.
What sets it apart
What you can check, not just take on faith
- The rules live in the database
- Permissions by role and by project do not depend on each screen remembering to apply them. An automated test checks that every API route goes through the check for the contracted module.
- Support without a trace does not exist
- Every table holding company data fires the support log, and a test fails if someone adds a new table without that connection. The log stores which columns changed, not the values.
- My account, with confirmations
- An email change goes through a confirmation link and the old email stays valid until you confirm. A password change asks for the current one and signs out other sessions. Both limit attempts, are logged and are blocked during a support session.
- Shared limits and scheduled jobs with a turn
- In production, the attempt limit is shared across servers and scheduled jobs take a turn so they do not run twice. Long lists warn when they are cut and say that totals cover only the loaded rows.
- Every credential has an owner
- API tokens stop working when the admin who issued them is removed, and support cannot issue them. Exporting data requires an admin. An invitation never chooses or hands over the invitee's credential.
What it doesn't do
The limits, stated up front
- Separation by role and by project covers money and staff; the rest of the data is separated by company, without distinguishing the project.
- The support log stores which columns changed, not the values.
- Changes made by a server process during a support session are attributed to the session, not to a person, and the log says so.
- This page describes software controls. It does not claim a certification or an external audit report.
Compared with what you use today
Compared with other ways to separate data and give support
- Shared folders with permissions
- A folder usually separates by user, not by project or role, and rarely records who opened what. Here the rule runs in the database and support access is logged.
- Support with a shared password
- With a shared password nobody knows who came in or why. Here there is a written reason, a 2-hour session and a log the company reads.
- A generic ERP with per-screen permissions
- If the restriction lives only on screen, a direct query skips it. Here the rule runs in the database, where that query passes too.
Frequently asked questions
What people usually ask before trying it
Can Renka staff see my company's data?
Only inside a support session: with a written reason, lasting 2 hours, with a fixed notice for whoever enters and a log you read. Without a session, they see only your company's profile card and the counters.
Where do I see what support did?
In Settings, under support activity. The owner and the company's admins see it, with the reason and how each session ended.
How do I change my email or password?
In My account. The new email is confirmed through a link and the old one stays valid until then. The password change asks for the current one and signs out other sessions.
Do you have a security certification?
This page does not claim any certification or external audit. It describes controls built into the software that you can review.
Next step
Let us review how your company, projects and roles would look
Tell us about your project and we'll show you this module with your own data, no commitment.
On the same topic
Other platform modules