mirror of
https://github.com/open-metadata/OpenMetadata.git
synced 2025-10-28 17:23:28 +00:00
* Updated generate_docs_schema * Updated generate_docs_schema * Updated generate_docs_schema * applied generate_docs_schema script * Revert the changes in this file --------- Co-authored-by: Tarun <tarun.p@deuexsolutions.com> Co-authored-by: Prajwal214 <167504578+Prajwal214@users.noreply.github.com>
2.0 KiB
2.0 KiB
| title | slug |
|---|---|
| teamHierarchy | /main-concepts/metadata-standard/schemas/entity/teams/teamhierarchy |
Team Hierarchy
This schema defines the Team entity with Hierarchy. Hierarchical teams are supported Organization -> BusinessUnit -> Division -> Department -> Group.
Properties
id: Refer to ../../type/basic.json#/definitions/uuid.teamType: Team type. Refer to team.json#/definitions/teamType.name: A unique name of the team typically the team ID from an identity provider. Example - group Id from LDAP. Refer to ../../type/basic.json#/definitions/entityName.description: Description of the team. Refer to ../../type/basic.json#/definitions/markdown.fullyQualifiedName: FullyQualifiedName same asname. Refer to ../../type/basic.json#/definitions/fullyQualifiedEntityName.displayName(string): Name used for display purposes. Example 'Data Science team'.href: Link to the resource corresponding to this entity. Refer to ../../type/basic.json#/definitions/href.children: Children teams. AnOrganizationcan haveBusinessUnit,DivisionorDepartmentas children. ABusinessUnitcan haveBusinessUnit,Division, orDepartmentas children. ADivisioncan haveDivisionorDepartmentas children. ADepartmentcan haveDepartmentas children. Refer to #/definitions/teamHierarchyList.isJoinable(boolean): Can any user join this team during sign up? Value of true indicates yes, and false no. Default:true.
Definitions
teamHierarchyList(array): Default:null.- Items: Refer to teamHierarchy.json.
Documentation file automatically generated at 2025-01-15 09:05:41.923720+00:00.