Give everyone a login. Not everyone the keys.
Operators, contractors, auditors: bring the whole plant into one system, each person signed in as themselves, and stay certain nobody can touch what they shouldn't.
Everyone signs in as themselves.
One account per person, even on a shared workstation, so every entry, check and sign-off carries a real name. No logins taped to the machine.
A real name on every entry
Each person signs in with their own account. Shared workstations can sign out on their own when left idle, so the next person starts as themselves.
Two-factor for anyone who wants it
Any user can add a second step at sign-in with an authenticator app, with backup codes for the day the phone is at home.
Guessing gets nowhere
Repeated wrong passwords lock the account for longer each time, and the sign-in form never says whether an email has an account. Every successful sign-in is logged.
Let anyone in, exactly as far as you choose.
A role says what someone can do. Site access says where. Set both per person, and take them away the moment the work is done. No IT ticket.
Sites, per person
A contractor reaches the one plant they work in. A manager reaches the plants they run. Every other plant shows as locked in their plant picker.
Roles you can shape
Start from a ready-made role or build your own, such as a view-only role for the customer's auditor. A role works the same at every site the person can reach.
Gone the moment you say
Deactivate someone and every session they have ends at once, on every device. Invitations that were never used expire after seven days.
They can't. The server says no.
The rules aren't just what's on screen. Bulk checks every action against the person's role and sites before it happens, so a clever workaround gets the same answer as the button.
- An operator deletes a batch recordPermission denied.
- A manager grants rights they lackYou cannot grant what you do not hold.
- An admin edits their own rolesYou cannot change your own roles. Ask another administrator.
- Someone removes the last super userCannot remove the last super user. Assign another super user first.
Checked where it counts
Every action is checked on the server, not in the browser. Hiding a button is a courtesy; refusing the request is the rule.
Nobody grants past their own reach
You can only hand out what you hold yourself, and nobody edits their own roles. The last super user always stays, so the plant can't lock itself out.
Every change on the record
Roles, permissions and site access changes are kept with who made them, when and at which site. Follow them in the audit trail.
Ready-made roles. Not a blank permissions screen.
Under the roles sit 369 action-level permissions across more than a hundred areas of Bulk: view, create, edit, delete, approve. You start from a role that already fits the job.
- Super user
- Entity admin
- Operator
- Manager
- Tablet user
- Invoicing
- Training
- Quality
- Dashboards
- Safety
- People
- Master data
- + Roles you build yourself
- 01
Pick a ready-made role
Twelve roles come with Bulk, from Operator and Quality to Invoicing. Use one as it is, adjust it, or build your own.
- 02
Invite people by email
Each invitation carries a role and the sites the person can reach. The link is valid for seven days.
- 03
Change it as the team changes
Promotions, contractors, leavers: change a role or site in seconds, or deactivate someone and they are signed out everywhere.
Questions, answered.
What is Bulk Access Control?
It's how Bulk decides who can do what, and where. Everyone signs in with their own account, each person gets a role and the sites they can reach, and the server refuses anything outside that.
Will operators see things they shouldn’t, like invoices?
No. Roles match real jobs, so an operator sees their line, not your books. On their home screen an area they can't open reads No access, search leaves it out, its pages won't open for them, and the server refuses anything outside their role.
How do I give a contractor or auditor access without risk?
Invite them by email with a role and only the sites they need; the invitation link is valid for seven days. For an auditor, build a view-only role of your own. When the work is done, deactivate them and every session they have ends at once.
How long does it take to set up?
Twelve roles come ready-made, from Operator and Manager to Quality, Safety and Invoicing. Pick one, adjust it or build your own, and invite people by email so they sign in as themselves.
What happens if someone tries to do something outside their reach?
The server refuses it, whatever the screen shows, because every action is checked against the person’s role and site access before it runs. Changes to roles, permissions and site access are recorded in the audit trail with who made them, when and at which site.
Can one person work at several plants?
Yes. Site access is set per person, so a contractor can reach one plant and a manager several. A person’s role applies the same way at every site they can reach.
Does Bulk support two-factor sign-in?
Yes. Any user can turn on two-factor sign-in with an authenticator app, with backup codes as a fallback. Repeated failed sign-ins lock the account for longer each time, and the sign-in form never reveals whether an email has an account.
Map your org chart onto real roles.
Start a free trial, invite your team and give every operator, lead and contractor the role and the sites they need. No card needed.
