Users
The people who access and operate the system
Add, import, configure, tag, secure, disable and audit the users who work inside Ofisync across branches, departments, groups, roles and notification preferences.
User profile
Access configured
Live business context
Add, import, configure, tag, secure, disable and audit the users who work inside Ofisync across branches, departments, groups, roles and notification preferences.
Why it matters
Every user profile controls identity, placement and access.
The Users module is where a company manages the people who can access Ofisync. Each user can belong to branches, departments and user groups, carry tags and custom fields, hold specific access configurations, receive notification settings and be fully disabled or revoked when access must be removed.
Give every user the right branch, department, group, role and access profile from the start.
Keep user records complete with notes, tags, custom inputs, notification settings and audit history.
Remove access quickly when a user is disabled, revoked or no longer allowed to use the system.
Guided workflow
From setup to daily execution.
Create the user record
Add a user manually or import users in bulk, then capture the user details, tags, custom fields and existing editable inputs required by the organization.
Place the user in the organization
Assign branches, departments and user groups so the user sits inside the right operating structure.
Secure access
Attach roles, permissions, access configurations and notification settings, then audit activity and revoke access when needed.
User administration fit
Built around people, access and organizational structure.
A new staff member joins a branch and department, needs access to specific modules, belongs to user groups, receives notifications in a preferred way and must leave an audit trail when they act. When that person leaves or loses authorization, access must be removed immediately.
How Users works in practice.
Scenario 1
A user profile starts with identity and structure
The admin creates a user manually or imports users in bulk. The record captures the user's profile details and places the person inside the correct branch and department.
Scenario 2
Custom inputs make the user record fit the company
The organization can add custom inputs for users and modify existing user fields, so the profile captures the information the company actually needs.
Scenario 3
Tags help classify and find users
Users can be tagged for grouping, search and operational context. Tags can support departments, responsibilities, access patterns or any internal classification the company uses.
Scenario 4
User groups connect identity to access
A user can belong to one or more user groups. Those groups can be used by the access model to decide what the user can see or do.
Scenario 5
Roles and permissions define what the user can access
Each user can have specific roles and permissions. This ensures the user only accesses the relevant data, actions and modules for their work.
Scenario 6
Access configuration can be user-specific
Beyond broad roles and groups, a user can have unique access configurations. This supports cases where one user needs access that differs from others in the same department or role.
Scenario 7
Notes and notification settings stay with the user
User records can include notes for internal context and notification information settings that control how the user receives relevant alerts.
Scenario 8
Audit logs make user activity traceable
Audit logs record important user-related actions, access changes and security-relevant activity so admins can review what happened later.
Scenario 9
Disabling or revoking a user removes access
When a user is disabled or revoked, their access to the system and data can be removed. This protects the workspace when someone leaves, changes responsibility or loses authorization.
User scenarios
Where user records become operational control points.
User scenario 1
New user onboarding
An admin adds a user, assigns branch, department, user groups, roles and access configurations, then confirms notification settings before the user starts work.
User scenario 2
Bulk user import
A company can import users in bulk, then map user details, branches, departments, tags, groups and access-related fields into the system.
User scenario 3
User revocation
When a user should no longer access the system, the account can be disabled or revoked so access to the system and data is removed.
Inside user management
A complete workspace for the people using the system.
The user workspace keeps profile details, branches, departments, groups, roles, permissions, tags, notes, custom fields, notification settings, audit logs and disable or revoke controls connected to each user.
Admins
User creation, bulk import, revocation, access configuration and audit logs
Department leads
Users in their departments, branches, groups, tags and operational assignments
IT and security
Disabled users, revoked access, notification settings and role-permission alignment
User records
What stays attached to each user
User access movement
Actions Ofisync can prepare from user changes
User view
User directory
Review users by branch, department, group, tag, role, access status and notification setup.
User view
Access posture
See which users have specific roles, permissions, groups and user-specific access configurations.
User view
Revocation audit
Track disabled and revoked users, including when access was removed and which actions were recorded.
Connected user modules
Modules that depend on user identity and access.
Role-Based Access
Define roles as collections of access items, assign action-level access rules, hide sensitive entity details and secure critical actions with MFA, audit logs and admin controls.
Notifications
Define Email, SMS, WhatsApp and On Screen notification channels, configure company-wide and personal preferences, send memos, and let users act directly from actionable notifications.
Multi-Tenancy
Run each organization on its own database with complete data isolation, then use branches and roles inside that organization when further separation is needed.
Ready to see it live?
Walk through Users with an Ofisync specialist.
We will map the demo around your business workflow, show the connected modules and help you identify the fastest path to rollout.