Vault structure

Every setting in the CtrlTMS configuration that names a piece of vault structure is listed here. None of them can be filled in until the thing it names exists.

How the pieces relate

One object type for teams and channels. A team and a channel are the same object type, separated by class. They are related things with the same lifecycle, and keeping them together means one workflow and one set of views covers both.

The Graph ID property. Every object CtrlTMS creates carries the Microsoft Graph identifier of the thing it represents. That identifier is how a second discovery run recognises a team it already created, rather than creating another one.

The Graph ID is not a user-editable field

It is written by CtrlTMS and read by it. Editing one by hand breaks the match, and the next run creates a duplicate rather than reporting a problem. Hide it from the metadata card, or make it read-only.

Members and owners. CtrlTMS keeps a team’s members and owners on the M-Files object, so the vault can answer who has access without asking Microsoft. Those are lookups to whatever object type represents a person in this vault — the same one CtrlSync’s employee configuration uses, if both are installed.

A workflow. Discovery creates objects; the workflow is what decides when one of them starts being acted on. In a CtrlTeams deployment this is where a discovered team is reviewed and then made active, which is the signal CtrlSync waits for.

CtrlTMS binds 29 settings to something that has to exist in the vault, 19 of them required. Everything below is generated from the shipping application, so nothing it needs is missing from this list.

Object types

Create these first; classes and properties hang off them.

Needed for	Configuration section	Required
Object Type	Team configuration	Yes
Object Type	Member configuration	Yes
Object Type	Channel configuration	Yes

Classes

Each belongs to one of the object types above.

Needed for	Configuration section	Required
Class	Team configuration	Yes
Class	Channel configuration	Optional

Value lists

Lookup properties below read their values from these.

Needed for	Configuration section	Required
Value List	Channel types config	Yes

Properties

The data type is not advice. A property of the wrong type cannot be selected for the setting at all.

Needed for	Configuration section	Data type	Required
Active Property	Common configuration	Boolean	Yes
Graph ID Property	Common configuration	Text	Yes
Graph URL Property	Common configuration	Multi Line Text	Yes
Team Property	Common configuration	Multi Select Lookup or Lookup	Yes
Display Name	Team configuration	Text	Optional
Description	Team configuration	Multi Line Text	Yes
Owners Property	Team configuration	Multi Select Lookup	Yes
Members Property	Team configuration	Multi Select Lookup	Yes
Groups Property	Team configuration	Multi Select Lookup or Lookup	Optional
Private Property	Team configuration	Boolean	Yes
Email Property	Member configuration	Text	Yes
Display Name	Channel configuration	Text	Yes
Description	Channel configuration	Multi Line Text	Yes
Channel Type Property	Channel configuration	Lookup	Yes
Members Property	Channel configuration	Multi Select Lookup	Yes
Owners Property	Channel configuration	Multi Select Lookup	Yes

Workflows

One per object type that the application drives through states.

Needed for	Configuration section	Required
Teams Workflow	Workflow configuration	Optional

Workflow states

States within the workflows above. Entering one is what triggers the work.

Needed for	Configuration section	Required
Create State	Workflow configuration	Optional
Created State	Workflow configuration	Optional
Archived State	Workflow configuration	Optional
Deleted State	Workflow configuration	Optional
Error State	Workflow configuration	Optional
Discovered State	Workflow configuration	Optional

Generated from CtrlTMS 0.25.6.0.

Check

• A team object can be created by hand with every property the configuration will ask for.
• The Graph ID property is text or multi-line text, and is hidden or read-only on the metadata card.
• If CtrlSync is also installed: the object type and class here are the ones CtrlSync synchronises, and the person object is the one its employee configuration uses.

Next

Set up CtrlTMS — step four, entering the Graph credentials.