ActiveManage has two distinct admin surfaces — the Admin Home (day-to-day operations) and the Architect Panel (build-time configuration). Knowing which to open for which task saves clicks and prevents accidental changes.
Admin Home
For everyday operational work — handling tickets, updating customer records, sending broadcasts, reviewing reports, processing approvals. Anyone with operations permissions lands here.
Architect Panel
For build-time configuration — defining datastores, designing forms, configuring permissions, setting up integrations, managing security. Restricted to administrators and developers.
Side-by-Side Comparison
- Admin Home: CRUD on records. Architect Panel: CRUD on the schema records live in.
- Admin Home: View a user. Architect Panel: Add a custom field to the user record.
- Admin Home: Approve a vendor application. Architect Panel: Define what a vendor application form should ask.
- Admin Home: Send a one-off broadcast. Architect Panel: Configure the broadcast template and audience rules.
- Admin Home: Read a report. Architect Panel: Define what queries that report runs.
Permissions
- Anyone in an operations group can see Admin Home.
- Only Architect group members can see the Architect Panel.
- Within Architect, fine-grained permissions control which sections are editable.
Worked Examples
- Support agent: Lives in Admin Home; never touches Architect.
- HR admin: Admin Home for user management, Architect to add a new custom field to user profiles.
- Developer: Architect Panel for configuration, occasional dip into Admin Home for testing.
- Product manager: Architect Panel for feature flags; Admin Home for usage reporting.