6.2.2.18 CapabilityCatalog
6.2.2.18.1 Purpose¶
What a system published as its capabilities and features, version by version. access validates roles against it, so a role can only hold capabilities some system actually checks, and products offer agent tools from it. The latest version received from each system is the one in force; a capability that disappears stays in existing roles but can no longer be granted.
6.2.2.18.2 Questions it answers¶
- Which capabilities and features does each system publish today?
- Which version of a system's catalog is in force, and since when?
- Which roles hold a capability no system publishes any more?
6.2.2.18.3 Fields¶
| Field | Type | Cardinality | Description |
|---|---|---|---|
id |
string (uuid) |
1..1 |
Key. |
system |
string |
1..1 |
e.g. farm, moochat. |
version |
string |
1..1 |
The release of the system that published it. |
catalog |
string (JSON) |
1..1 |
Capabilities and features with their descriptions, risk and data class, and the event types the system lets leave the platform, which the Webhooks API offers to Organizations. A capability's risk is read, write or admin, as OrganizationRoleCapabilityEnum and MoonitoringCapabilityEnum give it; access derives from it what a delegation, a join link and a service account may hold. |
published_at |
datetime |
1..1 |
|
received_at |
datetime |
1..1 |
|
created_at |
datetime |
1..1 |
6.2.2.18.4 Rules & constraints¶
- What a system published as its capabilities and features: access validates roles against it (a role can hold only capabilities some system published) and products offer tools from it.
(system, version)is unique. The latest received version of each system is the one in force; a capability that disappears from it stays in existing roles but can no longer be granted, and the Console flags those roles.