Down to the single field
Show the name and phone, keep the medical notes private. A hidden field is never sent to that person's screen at all.
Most systems give each person one role for everything. In Qik a role applies inside an area, so the same person can run one team, read another and see nothing of a third, right down to the single field.
No credit card. Qikbot is included.
Why it's different
Role-based access answers one question: what is this person? Real organisations need three. What can they do, in which part of the organisation, and to whose records. Qik answers all three at once.
One role per person, applied to everything: admin, editor or viewer.
A role is given inside an area and flows down to everything beneath it. You map your teams, branches and programs once, then say who does what in each.
Access to a kind of record is all or nothing.
View, create, edit and delete are separate, for every record type including the ones you define, and down to the single field. One form's responses can be opened to one team without opening the rest.
If you can see a record type, you can see all of them.
Every record in the area, only the ones a person owns or is assigned, or only the ones they take part in.
Nobody can say why someone can see something.
Ask why a person can or can't see a record and get the exact rule. The same rules are enforced on the server for the dashboard, your website, the API and Qikbot.
An example. Three people, one system, and each sees a different version of it.
All the way out to your apps
Access doesn't stop at the dashboard. Every website, portal and app you build on Qik gets layers of access that stack on top of each other, so a curated, personal experience for each person is already wired in.
Each layer adds to the one before, and the server checks every one. Data a person can't have is never sent to their browser. Whatever your use case, the logic for who can do what is already built.
How it works
Teams, branches and departments, nested the way your organisation really is.
Put someone in a position and they get what that position needs, and nothing else.
The dashboard, your website, the API and Qikbot all apply the same rules.
Permissions & privacy
Most tools offer admin or not-admin. Real organisations are messier: a team leader needs phone numbers but not medical notes, for their own branch and nobody else's. In Qik you can say exactly that, and it holds everywhere: the dashboard, your website, the API and Qikbot.
The basics, covered
The standard parts of access control are here too, working from day one.
Show the name and phone, keep the medical notes private. A hidden field is never sent to that person's screen at all.
Let someone see only the records they own, the records in their part of the organisation, or all of them.
Roles come with the position, so changing someone's job changes their access.
Bundle a set of access and hand it to a person, or to everyone who signs up to your app, in one step.
People can only pass on access they have themselves.
Ask why someone can or can't see a record and get an answer that traces every rule involved.
It works as the signed-in person. Anything that sends, deletes, publishes or moves money waits for approval.
A one-time code by email when someone signs in.
Who changed what and when, with the ability to roll it back.
Start today
Start a free trial and tell Qikbot what you need, or talk to the people who build it. Either way you begin with something that works.
No credit card. Your data stays yours, and you can export it any time.