Permissions attached to the document
Configure owners, groups and view or edit permissions around the approved access model. Embedding a document console in the Employee workspace does not remove those checks.
Learn More →CONFIGURABLE
EDMS Access & Retention
Govern who can see evidence—and for how long.
Apply role, group and linked-record access policies together with retention, archive and deletion workflows defined by organizational policy.
Learn More →NEXCOM // CONFIGURABLE/EDMS/ACCESS-RETENTION/
Operational scope
- Role and group permissions
- Relationship-aware document access
- Retention and archive rules
- Deletion approval and audit history
01FINANCE
02OPERATIONS
03PEOPLE
04STAKEHOLDERS
05EVIDENCE
CONNECTED CAPABILITY
How the workflow connects.
Capabilities are connected to common master data, permissions, workflows and evidence. Exact delivery is confirmed through the edition and implementation scope.
Retention as an organizational rule
Define record classes, retention expectations and the person authorized to archive or dispose of them. Operational schedules and regulatory requirements must be evaluated for the organization.
Learn More →Recovery is part of the operating model
Repository backups, recovery verification and administrator responsibilities should be documented. A storage policy is meaningful only when its required behavior is implemented and tested.
Learn More →CONTROLLED DELIVERY
Configuration is part of the product.
NexCom does not treat every listed workflow as automatically enabled. Edition selection, access rules, regional requirements, integrations and evidence obligations are defined and tested before production acceptance.
AVAILABLE
Supported by the current baseline.
CONFIGURABLE
Enabled through agreed project scope.
PLANNED
Proposed and subject to implementation.
NEXT STEP
Discuss requirements →Learn More →Map NexCom to your operating model.
Bring your processes, stakeholder groups, deployment boundary and priority integrations.