Configuring Enteprise Hub in Airtable

Prev Next

Plan availability

Enterprise Scale plans

Permissions

Super admins can/have:

  • Configure SSO and SCIM for their org.

  • Full visibility and admin rights over users and workspaces in the organization.

  • Visibility into on-domain users and any external user collaborating on an org-owned workspace, base, or interface.

  • Control Airtable licenses.

  • Ability to create new org units or grant super admin access, new org units through the admin panel that inherit the organization's default security policies.

  • Ability to configure SSO, SCIM, and domains.

  • Power to establish security policies that apply to all org units, by default. Rules for APIs and compliance tools such as EKM, DLP, and audit logs apply to the entire organization.

Org-unit admins have:

  • Visibility into specific org units where they are an admin.

  • Administrative rights for workspaces and user permissions on their org units.

  • Visibility into all org unit members, and any on-domain user or external user collaborating on an org unit-owned workspace, base, or interface.

  • Ability to grant org unit admin access.

User admins have:

  • Administrative rights over users.

  • Ability to manage groups and their memberships.

  • Ability to manage workspace, base and interface collaborations

Platform(s)

Web/Browser, Mac app, and Windows app

Related reading

This article is part 3 of 4 of the Enterprise Hub overview series.

Org units and admins in Enterprise Hub

  • Org unit creation: After enabling Enterprise Hub, super admins can create new org units to reflect the different real-world entities.

  • Org unit admin assignment: Assign users as org unit admins to manage users, resources, and settings within their designated org units.

Note

You can customize org unit logos to help users distinguish which org units host their resources and understand their locations.

Users, user groups, and org unit membership in Enterprise Hub

Note

To help determine which org unit user groups should live in:

  1. Identify the user groups and users most closely aligned to the org unit you are creating.  

  2. Ensure the default org unit should hosts the user group relevant to users across more than 1 org unit.

  3. Ensure the user group connected and used to manage features like org unit membership is hosted in the fault org unit.

User groups can be moved to the appropriate org unit via the admin panel or the move user groups API.

To move a user group to another org unit:

  1. Open your admin panel.

  2. Click Groups.

  3. Select the checkbox next to the group’s name you want to move.

  4. Click Actions.

  5. Click Move to another org unit.

  6. Select your preferred org unit.

  7. Click Move group.

Check out our Enterprise Hub article to learn how to org units within the Enterprise Hub.

You can manage users using an identity provider (IdP) sync, including SCIM (System for Cross-domain Identity Management), which allows automated user provisioning and de-provisioning.

FAQs

How do I decide which org unit a workspace should be hosted in?

  1. Workspace should live in the org unit that is most relevant to the users in that org unit.

  2. If a workspace is relevant to users across more than 1 org unit, it should live in the default org unit.

  3. Workspace can be moved to the appropriate org unit via the admin panel or the move workspaces API.

Next

Check out our Enterprise Hub example configurations article to continue to the last part of the Enterprise Hub overview series.