Admins

Admin and owner roles

An organization admin can open the elba admin portal and manage the security modules and settings available to the organization. The organization owner has admin access plus ownership responsibilities.

Each organization has one owner. Admins and the owner can still use the member experience when enrolled, but their administrative role controls access to the admin portal.

Open the Users page for your region:

• EU admin portal
• US admin portal

Manage admin roles

From Settings → Team → Users, an authorized admin can open an enrolled employee's row actions and:

• Promote a member to admin
• Demote an admin to member
• Manage the employee's group memberships
• Enroll or unenroll an eligible employee

The current owner can also transfer ownership to an eligible admin. Transferring ownership makes the selected admin the new owner and changes the previous owner to an admin.

Role changes affect access to administrative data and controls. Confirm the employee's responsibilities and follow your organization's least-privilege and offboarding process before changing a role.

See User management for enrollment, group, and role-management instructions.

What a new admin receives

When an active employee is promoted to admin, elba sends a promotion email with a link to the admin portal. The new role applies to subsequent authenticated access; if the employee already has elba open, ask them to refresh or sign in again before troubleshooting missing admin controls.

Administrative communications

Admin communications depend on the enabled modules, connected sources, playbooks, and organization settings. They can include operational emails, connection-health messages, or alerts produced by configured workflows. This is not an exhaustive list, and there is no single delivery schedule that applies to every admin notification.

For playbooks with a Notify admins action:

• The workflow can target selected owners or admins where recipient selection is available.
• If no specific recipients are configured, the supported workflow can notify the organization's owner and admins.
• Delivery uses the configured organization channel and, where enabled, the recipient's personal communication preference.
• A deliverable channel and a healthy integration are required for chat delivery; email can be used by the delivery logic when a selected chat channel is unavailable for that user.

Where per-user communication preferences are enabled, an admin can update a person's channel from Settings → Team → Users. Available choices depend on the connected Slack, Microsoft Teams, or Google Chat integrations. See Members and Sam for employee-facing channel and reminder settings.

Recommended access review

Review administrator access whenever responsibilities or employment status change:

1. Open Settings → Team → Users and filter or scan for the Admin and Owner role badges.
2. Confirm that every admin still needs administrative access.
3. Demote administrators who no longer require the role.
4. Transfer ownership before the current owner leaves the organization.
5. Review connected integrations and workflow recipients for references to former administrators.

Unenrolling or demoting a user in elba does not replace deprovisioning in your identity provider or connected applications. Complete those changes in the authoritative systems as part of your offboarding process.