Security & Access Control

Start with responsibility

Define what each person needs to enter, review and approve. SERP roles control permitted areas, while actual page and action access must be tested. Users should establish their company and relevant fiscal or location context before processing.

Separate sensitive workflows

CRM access differs from accounting customer access. Payroll administration differs from employee self-service. Document viewing, editing and release use distinct permissions, while audit lookup is restricted. These boundaries should be demonstrated with representative accounts.

Review integrations and activity

Keep credentials and connection settings with authorized administrators. Use activity and audit evidence where permitted to investigate changes. AI provider configuration needs a data-boundary review because context and tool data can leave the ERP.

Validate controls in your deployment

The website makes no unsupported certification, authentication or guaranteed-availability claims. Confirm the enabled functions, role scope and operating procedures with the implementation team. Review both allowed and denied actions when testing access.

How does SERP control user access?

SERP uses user accounts, assigned access roles and permission-controlled areas and actions. Company availability and branch/location restrictions should be reviewed separately from page permissions.

Separate entry, review and administration

A user who enters a sales record need not have the authority to approve it or change company configuration. HR profile access, payroll processing and employee payment also represent different responsibilities. Test representative roles using both permitted and denied actions.

Investigate changes with context

User Activities Inquiry and authorized audit views support investigation. Retain the company, user, transaction reference and date when discussing an issue. A visible menu alone does not prove that every action is permitted.

Review documents, conversations and integrations

Document review/release permissions differ from attachment access. Chat group membership controls conversations and files. Integration credentials and AI provider settings belong with authorized administrators; review what data leaves the ERP for each service.

Questions for the deployment discussion

Confirm account management, role review, backup operations, hosting responsibilities and any additional authentication requirements. This website does not claim unverified security certifications or deployment-wide technical guarantees. Read the roles and permissions guide.