Team

Default Team

By default MechCloud defines only one team - Default (Managed). This is an unshared but managed team.

• All authenticated users are by default members of this team but have only contributor and cloudadmin roles on this team.

• As authenticated users are not assigned creator role on this team, an authenticated user can't register custom components (Frame, Layout, External Page, Component) on this team.

Parameters

Parameter	Description	Editable for an existing team	Tutorials / Demos / Sample Code
Single Person	Enable this to create a shared and unmanaged team without configuring advanced team parameters. Useful for solopreneurs or anyone who starts with one person team but may grow to 2-3 members in the future. This is to keep MechCloud UIs simple by default for small teams. Disable this to see advanced team parameters.	No
Shared	In a shared team, a team member can see and access the assets created by other team members which is not possible in case of an unshared team. In a shared team, two members can't register or create two or more resources of same type (e.g. Frame).	No
Managed	A managed team inherits custom components (e.g. frames, layouts) registered under its parent team. It is not allowed to register or override custom components under a managed team.	No
Owner Team	This parameter will be visible for managed teams only. An owner team is the one which this team will inherit custom components from. Only a shared team can be an owner team. However, this shared team must be created by the same user who is creating a new team.	No
Custom Components Host	This parameter will be editable for unmanaged teams only while creating a new team. This parameter is read only for a managed team and inherited from its parent team. This is used to specify the url of a micro app which will be used to load custom components created by third parties. This parameter can be overridden at the site level for unmanaged teams only.		Reference micro app - https://github.com/mechcloud/mechcloud-demo-microapp1
OIDC Proxy	This parameter will be editable for unmanaged teams only while creating a new team. This parameter is read only for a managed team and inherited from its parent team. This is used to specify the url of an OIDC (OpenId Connect) proxy which allows MechCloud to communicate with any third party REAST API (e.g. Cloudflare, MongoDB Atlas etc) without storing api key for any such APIs.		Reference - https://github.com/mechcloud/mechcloud-oidc-proxy
Members	Specify email ids of all the users who should be member of this team. Add 'authenticated' group as member if you want all authenticated users to be the members of this team. A user/group must be added to the members before it can be assigned any role on the team.
Creators / Contributors / Cloud Admins	See Roles section.

There are two important aspects of a team which can be configured while creating a team -

Shared vs Unshared

• A shared team is the one where any asset (e.g. Site, Frame, Layout etc) created by any team member is visible to all the other members of the team. In a shared team, one can't create two resources of same type (e.g. Frame) using same metadata (name, title, code etc). This restriction is not there for an unshared team but a member of an unshared team can't see custom components registered by other team members.

Examples

• As a small startup, you can create two teams - Employees and B2CCustomers. Here you may choose Shared for Employees team while unshared must be chosen for the B2CCustomers team. Employees team will have developers and testers where testers need to see the Frames, Layouts etc registered by developers so that testers can use these to create test websites and validate these components before these components can be made available to the B2C or B2B customers. B2CCustomers team should be unshared as you don't want one user to see the data of another user when the members of this team are not related to each other in any way.

Managed vs Unmanaged

• A team can either be managed or unmanaged. A managed team has some restrictions (e.g. can't register its own frames/layouts/external pages/components) imposed on it and inherits certain things (frames/layouts/external pages/components) from its parent (unmanaged) team.

• If you configure a team as managed then you will need to select an unmanaged team as a parent for this team. It means you must have at least one unmanaged team created before you can create one or more managed teams.

Examples

• You can create two teams - Employees and Customers where Developers team is configured as unmanaged while Customers team is configured as managed (by Developers Team). Now whatever assets (e.g. Frames, Components, External Pages etc) will be registered in the Developers team will be visible in the Customers team but members of the Customer team will not be able to register their own custom components (frame, layout etc) or edit the details of custom components inherited from the parent team.

Single Person Team

A single person team is a shortcut to create a shared but unmanaged team. This is suitable for startups / agencies which starts with and remains one man show for a short/long time but may grow to 2 or 3 persons in future. This is something which will be very common in an AI powered era.

Roles

MechCloud defines some roles which are specific to the Team resources. Each role is associated with a certain module (Site builder, Infrastructure management). These roles are as follows -

Module	Role	Comment
Site Builder
	Creator	This role allows a user to register frames, layouts, external pages and components under a team. Note - This role must be explicitly assigned to the user who has created a team and so have admin role by default. Single person teams are an exception of this rule where team admin is automatically added to all the roles associated with the Team resource type.
	Contributor	This role allows a user to create sites and site nodes under such sites in a team. Note - This role must be explicitly assigned to the user who has created a team and so have admin role by default. Single person teams are an exception of this rule where team admin is automatically added to all the roles associated with the Team resource type.
Infrastructure
	Cloud Admin	This role allows a user full access to Infrastructure module where a user with this role can add cloud / REST accounts etc. Note - This role must be explicitly assigned to the user who has created a team and so have admin role by default. Single person teams are an exception of this rule where team admin is automatically added to all the roles associated with the Team resource type.