Product and implementation guide
Organize the people process
Company Management brings company and HR work into an ArcApps application with dedicated portal audiences. Begin by listing the processes included in your subscription: recruitment, onboarding, employee records, attendance, leave or other agreed work. Assign an HR owner and identify which policy determines each approval. The application supports the process; it does not establish employment rules or replace professional advice.
Example: a new employee
Prepare the approved employee details and an onboarding task list. Identify who confirms the start date, who authorizes access and who checks completion. Keep candidate information separate from employee access until the agreed transition occurs. Test a changed start date and a missing document using synthetic records. Do not assume that every candidate automatically receives an employee account.
Attendance, leave and corrections
Before recording live attendance or leave, confirm schedules, approvers and correction responsibilities. Test partial days, an unavailable approver and a returned request according to your organization's rules. Employees should understand whether a request is submitted or approved and where to ask about an incorrect record. Payroll or statutory calculations require validation by the appropriate qualified owner.
Keep each audience's access distinct
Review HR, employee, candidate and customer access separately. A customer portal does not imply access to employee records. A manager should see only the information needed for approved responsibilities. Confirm export, retention and account-removal procedures with your implementation team. For a rollout checklist, read the employee portal guide .
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support