Business Portals & Owner Governance
Assign employee portal profiles, distinguish BU accounts and review owner-approved daily audit reports.
Open interactive lesson and quizWhat you will learn
- Assign permissions independently of job titles
- Use approved owner portal sessions
- Review daily activity in the BU timezone
An organization needs HR, engineering and cashier access without giving every employee a full BU account.
Lesson 1
Organization masters and employee IDs
Administration → Employees → Organization setup maintains departments, career levels, pay levels and country/state facilities. Employee forms select configured options. A server-side counter allocates the formatted employee ID once; employment status changes preserve the ID and history. BU accounts are associated by the same work email, while employee-only staff continue to use email verification codes.
Lesson 2
Identity and access are separate
Employee-only accounts use short-lived codes sent to the email on their active employee record. Each service has its own portal. Named profiles define employee record scope and individual People, Finance and POS permissions; a job title does not grant permissions. Portal configuration is performed by authorized BU users. Employee-only profiles grant operations such as time reviews, benefits enrollment handling, cashier work and storefront fulfilment. Explicit employee and career-level exclusions protect records across reads, changes, downloads and exports. An employee linked to a BU account uses BU credentials and the optional passkey. Profile changes take effect on subsequent requests.
Lesson 3
Owner approval for each session
The platform administrator registers the business owner address during BU setup; its owner-only welcome email includes a SupaAdmin invitation. BU managers do not receive owner access through their normal BU role. An owner requests a session, the platform reviews it, and an eight-digit code is emailed after approval. The code is single-use, limited to the requesting browser and valid for ten minutes. A new session requires another approval.
Lesson 4
Export access and operational lists
Data Handler exports subscribers, suppression lists, users, employees, roles, role permissions and operational records. Select fields, preview and download; the client follows server pages through the full permitted result. Data export is required with the source module permission. HR exports preserve employee exclusions, and credential material is excluded. Effective role permissions includes defaults and role overrides; individual user overrides are exported separately.
Lesson 5
Daily reports and access changes
SupaAdmin groups recorded BU and portal events by the business unit timezone. Reports remain scoped to that BU and exclude credential fields. Owners can disable BU users after confirming the exact email and reason. A business suspension blocks all of its portals and requires platform reactivation.
Practice · Review a portal access profile
- Open Administration → Employees → Portal access with User administration permission
- Create and assign a profile containing only required portal permissions
- Review owner access and the daily audit workflow with your platform administrator