Components - Airtable admin panel
  • 26 Sep 2024
  • 2 Minutos para leer
  • Oscuro
    Ligero
  • PDF

Components - Airtable admin panel

  • Oscuro
    Ligero
  • PDF

The content is currently unavailable in Spanish. You are viewing the default English version.
Resumen del artículo

Plan availability

Enterprise Scale only

Platform(s)

Web/Browser, Mac app, and Windows app

Related reading

Overview - Enterprise Admin Panel

Airtable terminology

Admin panel - A centralized set of tools to help admins manage their organization’s Enterprise account. It's a designated surface that includes ways for admins to view and manage users, groups, reports, bases, and more

Components are standardized building blocks for apps in your organization. The admin panel’s “Components” page allows admins to view high-level information about their organization or org unit’s (Enterprise Hub only) component usage. It also provides a portal to create or manage development bases, transfer component ownership, and unpublish components from the org’s component library.

Using the components page in the admin panel

Accessing the components page

  1. Open your admin panel.

  2. Click Components.

Navigating the components page

When you access the “Components” page you’ll see a layout similar to the image shown below:

You’ll be able to:

  • Search for a component by it’s name

  • Filter to show All components, only Field components, or only Table components.

  • Click the + Publish a component button to create and publish a new component in the builder hub

  • Below these options you’ll see a list of all of the components associated with your org or org unit showing:

    • Component - The name of the component

    • Type - The type of component created (“Field” or fields, “Table” or tables, or “Table and more” with more typically representing automations or interfaces)

    • Owner - The org user who currently owns the component

    • Last published - The last time the component was published (i.e. new updates were added in the development base)

    • Audience - The audience that is able to use / add the component (Learn more here)

    • Times added - The number of times the component has been added

    • Org unit - (Enterprise Hub only) The org unit where the component can be used

Note

Most of the column headers can be clicked to sort the list of components in ascending or descending order by the column of your choice.

Clicking the icon to the right of a component that is listed on the page will open a menu where you can:

  • Go to development base - Navigate to the builder hub location containing the development base where this component is managed

  • View details - Navigate to a more detailed view of information related to a specific component

  • Transfer ownership - Covered in the “Transferring ownership of components” accordion below

  • Unpublish from library - *CAUTION Unpublishing will delete the component / development base. Any connected components will continue to exist, but the configuration of any managed fields, tables, automations, and interfaces that make up the component will continue to be locked unless they are converted to unmanaged. This action cannot be undone.

Transferring ownership of components

  1. Navigate to the admin panel for your organization.

  2. Next, click on Components from the left side of the page.

  3. Browse or search for the component that you want to transfer. You’ll see some helpful information listed so that you can identify the name, type, current owner, and other usage metadata related to the component.

  4. Click the icon to the right of the component that you want to transfer.

  5. Click Transfer ownership in the menu that appears.

  6. From the dropdown menu, choose the appropriate user to transfer ownership of the component.

  7. Finally, click Transfer.

A few notes:

  • Only members of the same org unit are eligible to become the new owner.

  • The new owner will be added as a collaborator to the development base.

  • The original owner will not be removed as a collaborator from the development base.


¿Te ha sido útil este artículo?