Tenant Administration Console - Alforse

Console is the organization administration surface, separate from the Deals workspace. It requires the admin module permission (see Roles & Permissions) and only ever operates on the current tenant.

What you can manage

Area	Capabilities
Settings	Tenant-wide settings and bootstrap status
Subject companies	Create, update, and delete the subject companies contracts are written under
Members	List and update members, preview what happens before offboarding someone, offboard a member, transfer tenant ownership
Invitations	Create, list, resend, and cancel member invitations
Roles & permissions	List roles and the tenant’s full permissions overview; update a role’s module permission matrix and workflow-control levels
Notification channels	Create, update, and test the channels collections reminders are delivered through
Data plane connections	Configure or clear a customer-owned data plane connection (relevant to the `enterprise_hybrid` edition)

Every one of these maps directly to an endpoint under /tenant-admin — see Tenant Administration API if you’re scripting a setup instead of clicking through the console.

Member offboarding and ownership transfer

Offboarding a member and transferring tenant ownership are treated as sensitive, auditable actions rather than a simple status flip:

GET /tenant-admin/members/:id/handover-preview shows what would be affected (assigned contracts, owned views, etc.) before you commit.
POST /tenant-admin/members/:id/offboard performs the offboarding.
POST /tenant-admin/owner-transfer moves tenant ownership to another member.

Notification channels

Channels configured here are what Collections reminders and other tenant notifications are delivered through. Test a channel immediately after configuring it (POST /tenant-admin/notification-channels/:id/test) rather than waiting for the next scheduled reminder run to find out it’s misconfigured.