Administration
Configure users, roles, firm settings, audit, and developer access.
Administration gives firm administrators one place to manage the CaseWizard tenant, access policies, users, integrations, and developer tools.
Plan your administration work
Use the administration areas according to the task you need to complete. Start with the firm profile and settings, then configure access for users and roles. Review audit logs regularly, and create developer credentials only when an integration requires them.
| Area | Path | Purpose |
|---|---|---|
| Account Profile | Company, Billing, Subscription | Manage firm identity and Stripe billing |
| Users | /administration/users | Create and manage user accounts |
| Roles and Permissions | /administration/roles-and-permissions | Define permission trees and assign access |
| Audit logs | /administration/audit-logs | Review security and activity history |
| Settings | /administration/settings | Configure registration, login, and document storage |
| Abbreviations | Administration | Manage shortcuts for text expansion |
| Fields | Administration | Configure custom case detail classes |
| Languages | Administration | Configure UI localization |
| Organization Units | Administration | Manage the firm's hierarchy |
| API Keys | /administration/api-keys | Create programmatic access tokens |
| OAuth Clients | /administration/webhooks | Configure client-credentials applications |
| Webhooks | /administration/webhooks | Send HTTP event callbacks to an integration |
Set up a new firm
Account profile
The account profile includes the firm's legal name, address, phone, and email. Billing and subscription information use Stripe billing. Keep company information current so administrators have an accurate record of the tenant.
Switching document storage providers does not migrate existing files. Coordinate any provider change before changing the firm setting.
Access and permissions
Use Users to manage individual accounts and Roles and Permissions to control what those accounts can do. Permission resources include cases, people, documents, calendar, billing, reports, users, roles, audit, integrations, and webhooks. Give each person only the access needed for their work.
Developer access
Use API Keys for scoped API access with X-Api-Key authentication. Use Webhooks for signed event callbacks and OAuth Clients for client-credentials applications. Store secrets securely and revoke credentials that are no longer needed.