Component Types Table (Beta)

The Component Types table gives organization admins one place to see every component type, instead of opening workspaces one by one. This is in beta, so the design and behavior may change as we gather feedback.

This article covers why the component type table exists, what it shows, how to open and manage a component type, how to edit matching types together, and what the beta doesn't do yet.

Each workspace has its own metamodel, so the same component type, such as Application, can exist in many workspaces. Until now, checking how a type was set up meant opening each workspace and managing them individually. As we move toward a global metamodel, the component types table lists them all together, just as the global fields table lists fields.

Organization admins can enable the component type table beta in Organization settings. Under Features, find the toggle and opt in.

Each row is a component type that exists in the organization. The table shows the type's name and the number of workspaces it exists in. Use search and sort to find a type quickly.

Component types with the same name can differ from workspace to workspace, for example in their fields, styling, or description. The variation page groups types that share the same name and the same fields into one variation. Here we can see the Application component type with multiple variations; this is because the fields applied to each instance are different.

A type that has a single variation (even if it exists in multiple workspaces) shows as a simple overview page where you can manage component type details.

When a variation covers several workspaces, edits can be applied to the whole group at once instead of workspace by workspace. From the details page, an admin can:

The change applies to every workspace in that variation.

Currently, it is not possible to combine multiple variations into one, but it is on the roadmap.

Select a component type to open its details page. The page shows where the type is used across the organization, so you can see the impact of a change before you make it. During the beta, this list will change as we improve impact analysis on the component type.

Beta feedback shapes what Ardoq builds next. To share yours:

OR

Feedback is most useful when it explains the situation. Try a job story: “When [situation], I want to [action], so I can [outcome].” Examples we’d like to hear: how you find duplicate or inconsistent types today, what you’d want to change across workspaces at once, and what’s missing from the details page.

For questions about the beta, use the in-app chat or contact your Customer Success Manager.

Can I still create types and manage them at the workspace level?

Yes, managing component types inside a workspace works as before.

Does the table replace managing component types in a workspace?

Partially. You can create and manage component types centrally in the component types table. However, deletion still resides in the workspace.

Will editing a variation change my data?

Edits change how the component type is defined, such as its fields, styling, and description, in each workspace in the variation.

Why do two types with the same name appear as separate variations?

They differ in their fields, so they are grouped separately.