Service capabilities
An index from what you want to do to the page that documents it. Feature list is the same ground organised by what a service offers rather than by page.
Setting up
Section titled “Setting up”| Capability | Covered in |
|---|---|
| Create a service | Create a service |
| Find and pin services in the catalogue | Create a service |
| Set team visibility at creation | Create a service |
| Decide what belongs in one service | Set up a new service |
| Name, description, department, owner | Settings reference |
| Tags | Settings reference |
| Icon, accent colour, banner | Settings reference |
| Choose which modules appear | Keep a service tidy |
| Create an asset of any type | Services quickstart |
The asset library
Section titled “The asset library”| Capability | Covered in |
|---|---|
| Find everything the service has made | Asset Library |
| Filter by file type, date, and size | Asset Library |
| Metadata captured automatically | Asset Library |
| Define custom metadata fields | Asset Library |
| Make a field required at upload | Asset Library |
| Scope a field to certain asset types | Asset Library |
| Track licence and rights expiry | Asset Library |
| Upload files | Asset Library |
| Folders and collections | Asset Library |
| Lifecycle states | Asset Library |
| Rights expiry filters | Asset Library |
| Usage analytics | Asset Library |
| Find duplicate files | Asset Library |
| Why asset and artifact counts differ | Artifacts and assets |
People
Section titled “People”| Capability | Covered in |
|---|---|
| Add an individual member | Manage people and access |
| Link a platform team | Manage people and access |
| Roles and what they allow | Manage people and access |
| Why there is no per-module access | What a service is |
| Audit log and its filters | Manage people and access |
| Tell human, AI, scheduled, and system actions apart | Manage people and access |
| Export the audit log | Manage people and access |
Publishing
Section titled “Publishing”| Capability | Covered in |
|---|---|
| Set the internal publishing ceiling | Control what gets published |
| Allow or block external publishing | Control what gets published |
| Restrict which external publishers may be used | Control what gets published |
| Check who can reach an item | Control what gets published |
| Why a ceiling is not a default | What a service is |
Understanding a service
Section titled “Understanding a service”| Capability | Covered in |
|---|---|
| Every artifact type and what it connects to | Artifacts and the Artifact Map |
| See every connected artifact | See how everything connects |
| Filter the map to one dependency chain | Artifacts and the Artifact Map |
| Collapse the map into groups | Artifacts and the Artifact Map |
| Filter the map by artifact type | See how everything connects |
| Find out what the map excludes | See how everything connects |
| Work out what breaks if you delete something | See how everything connects |
| Find orphaned content | See how everything connects |
Housekeeping
Section titled “Housekeeping”| Capability | Covered in |
|---|---|
| Set a friendly URL | Keep a service tidy |
| Hide a service from the catalogue | Keep a service tidy |
| Duplicate a service’s configuration | Keep a service tidy |
| Archive a service | Keep a service tidy |
| A periodic review worth doing | Keep a service tidy |
Things a service does not do
Section titled “Things a service does not do”| Not available | Detail |
|---|---|
| Sharing content between services | A service is a boundary. Content belongs to one |
| Per-module membership | Membership is service-wide |
| Publishing by itself | Content Access is a ceiling; each item still chooses |
| Copying content when duplicating | Duplicate copies configuration, not work |
| Hiding content with module toggles | Toggles change what is shown, not who may reach it |