Email and SMS settings
Control the accounts and verified numbers used for invoices, job photos, reminders and customer communications.
- Verified sender accounts
- SMS number status
- Communication consistency
Settings and security
DOP Settings & Security helps owners and administrators manage users, roles, company data, login flows, integrations, taxes and activity history from one controlled foundation.

Users, roles, company data, activity history and operational settings that keep the rest of DOP consistent.
Bring your real team structure. We will map which users need access, which roles should be limited and which company settings affect jobs, invoices and payroll.
Least access
roles aligned to real responsibilities
1 source
company data reused across modules
Audit trail
activity history for important changes
Security is operational control
As the team grows, access cannot live in memory. The wrong user can see payroll, miss a module, keep old permissions or make changes nobody can trace. DOP gives administrators a clearer way to control the foundation behind daily operations.

Administrative modules
These controls protect the system that runs the work: who can enter, what they can do and which master data feeds the operation.
Create accounts, assign roles, link employees or clients, send invitations and remove access when needed.
View controlDefine navigation and action permissions so office, finance, supervisors and admins only see what they need.
View controlMaintain contact info, business hours, taxes, email, SMS, Stripe, positions and settings used by other modules.
View controlAudit who created, edited, deleted or sent important records, with date and action context.
View controlCompany Data
The company configuration is not just a profile. It can affect invoices, Booking Engine, taxes, payments, messages, payroll setup and how teams understand the working day.

Control the accounts and verified numbers used for invoices, job photos, reminders and customer communications.
Connect payment processing and review transaction fee context before online payments depend on it.
Maintain regional tax settings and payment descriptions that can flow into invoice and finance workflows.
Set working schedules, time zone and employee positions so other modules inherit reliable context.
Users, roles and login
DOP separates the access account from operational records like employee or client. That matters when one person needs system access but also has a role in the business.
Confirm the email, avoid duplicate accounts and decide whether the user should be linked to an employee or client.
Use the minimum access needed: dispatch, accounting, supervisor, admin or another role that matches real responsibility.
Send the invitation, let the user verify by email code and select the correct company when needed.
Update permissions, force session logout or remove access when people change responsibilities or leave the company.
Activity Feed
When something changes, your team needs more than guessing. Activity Feed creates a practical trail for admins and supervisors to investigate system actions.
Review the user, date and action type behind important records.
Filter by activity type, search relevant terms and open expandable details when available.
Use the feed as the audit trail, then open the original module for the full operational record.

Admins decide which roles can view sensitive modules like payroll, reports or settings
Role changes can affect multiple users, so updates should follow real responsibilities
Company data should be reviewed before invoices, payments, messages or taxes depend on it
Activity Feed supports investigation, but the source module remains the place to inspect full details
Link access control with employee records, roles and team context.
View pageProtect sensitive performance, finance and payroll visibility with the right permissions.
View pageKeep taxes, payment settings and transaction workflows aligned with company data.
View pageBring your current roles, users and settings questions. We will show how DOP can structure access and company data around your real operation.
A user is the login account. An employee is an operational record. A person can have a user account linked to an employee when they need access to DOP.
Yes. Roles can control navigation and actions, helping administrators give each person the access needed for their responsibility.
Company Data can feed invoices, communications, payments, taxes, positions, working hours and other module behavior. It should stay accurate.
No. Activity Feed is for audit and investigation. The original module remains the place to inspect and update the record.
Bring your current roles, users and settings questions. We will show how DOP can structure access and company data around your real operation.
