FEATURE · LIVE DEMO ON THIS PAGE
Who gets in, what they see and what was recorded.
Users and roles, company data and the activity feed. What decides how far each person can go inside DOP — and how you investigate afterwards what happened.
What you see here is not a video: it is the real feature, running.
- the login account and the operating record
- User ≠ employeethe login account and the operating record
- the navigation and actions each one gets
- By rolethe navigation and actions each one gets
- feeds invoices, taxes and working hours
- Company datafeeds invoices, taxes and working hours
- for audit, not for editing
- Activity feedfor audit, not for editing
THE DEMO · INTERACTIVE · CLICK ANYTHING
Don't watch it. Use it.
Who did what and who can do what: review the roles, change a permission and follow the trail in the activity feed. Every screen responds.
EVERYTHING IT CAN DO
Control is not a checkbox: it is a structure.
Users and employees
The user is the login account; the employee is the operating record. A person can have both when they need access to DOP.
TWO DIFFERENT THINGS
Roles and permissions
Roles control navigation and actions, so each person gets the access their responsibility needs.
ACCESS BY RESPONSIBILITY
Company data
It feeds invoices, communications, payments, taxes, positions and working hours. Keeping it accurate matters.
AFFECTS EVERYTHING
Activity feed
For auditing and investigating what happened. Editing still happens in the module it belongs to.
AUDIT
Financials, restricted
Financial and payroll context is shown only to authorized users.
NOT EVERYONE SEES ALL
Grow without losing control
When new people join, their role defines what they can do from day one.
READY TO GROW
NOT A LOOSE MODULE
Access decides how far you can delegate.
An operation grows when the owner can hand off tasks without handing off control. That gets configured here, not improvised later.
- The role decides which modules each person sees.
- Company data feeds invoices, taxes and working hours.
- The activity feed is for investigating, not editing.
- Financial and payroll context stays with who should see it.
WHERE THIS CONTEXT FLOWS NEXT
Settings & Security FAQ
- What is the difference between a user and an employee?
- A user is the account someone signs in with. An employee is the person who does the work. A field worker can exist as an employee without an account, and you create one when they need to sign in.
- Can roles limit which modules a person sees?
- Yes. Roles can control navigation and actions, helping administrators give each person the access needed for their responsibility.
- Why does Company Data matter?
- Company Data can feed invoices, communications, payments, taxes, positions, working hours and other module behavior. It should stay accurate.
- Is Activity Feed used to edit records?
- No. The feed is for knowing who changed what and when. To edit, you go to the module where that data lives.
THE CLOSE
Delegate without losing control.
We help you define roles and permissions for your operation, with the structure you need to grow.
30-minute demo · no forced migration
