Action Logs
Bitbucket Server
Catalog News Articles
Catalog Technologies
Code Repos
Comment Replies
Diagram Contents
Diagrams
Flows
Health
Landscape Templates
Landscape Thumbnails
Model Connections
Model Objects
News
Organization Billing
Organization Icons
Organization Landscapes
Organizations
Organization Technologies
Organization User Invites
Organization Users
Share Link
Share Link Options
Support
User
User Notifications
User Goals
Version Reverts
Find Landscape
Headers
Path Parameters
Query Parameters
notion, miro, confluence, sharepoint, powerpoint Response
user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service curved, straight, square top-left, top-center, top-right, right-top, right-middle, right-bottom, bottom-right, bottom-center, bottom-left, left-bottom, left-middle, left-top top-left, top-center, top-right, right-top, right-middle, right-bottom, bottom-right, bottom-center, bottom-left, left-bottom, left-middle, left-top area, box actor, app, group, component, store, system user, api-key, notification-key, service batch user, api-key, notification-key, service current, draft context-diagram, app-diagram, component-diagram user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service context-diagram, app-diagram, component-diagram model object id this object belongs to
current, draft context-diagram, app-diagram, component-diagram user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service diagram id this flow belongs to
alternate-path, subflow, outgoing, parallel-path, reply, self-action user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service outgoing, bidirectional live, future, deprecated, removed catalog technology ids assigned to this model
user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service IDs of the groups this model object belongs to
Use either urlDark or urlLight
Icon that only works on dark backgrounds
Icon that only works on light backgrounds
Generic key value store used for creating custom integrations
valid, invalid programming, data, markup, prose azure-devops-repo Parent model object ID, null for the root level model object
live, future, deprecated, removed Team IDs that own this model object, does not propergate up or down
Model object (+child diagram, diagram groups and flows) can only be edited by owners and admins
Catalog technology IDs assigned to this model
actor, app, component, group, root, store, system Child diagram IDs
Child model object IDs, only one level down
user, api-key, notification-key, service Parent model object IDs for the whole hierarchy, ending with the root model object
user, api-key, notification-key, service Short summary of the object shown as the display description
user, api-key, notification-key, service blue, green, yellow, orange, red, beaver, dark-blue, purple, pink, white, grey, black aws, azure, gcp, microsoft, salesforce, atlassian, apache, supabase data-storage, deployment, framework-library, gateway, other, language, message-broker, network, protocol, runtime, service-tool Use either iconUrlDark or iconUrlLight
Technology color used in diagrams
blue, green, yellow, orange, red, beaver, dark-blue, purple, pink, white, grey, black Icon that only works on dark backgrounds
Icon that only works on light backgrounds
Long verbose name
Service provider that provides this technology
aws, azure, gcp, microsoft, salesforce, atlassian, apache, supabase Restriction on which model object or connections this technology can be added to
actor, app, component, connection, group, store, system Type or category of technology
data-storage, deployment, framework-library, gateway, other, language, message-broker, network, protocol, runtime, service-tool user, api-key, notification-key, service Whether the technology is disabled and not visible to users
Use either iconUrlDark or iconUrlLight
Organization that owns this technology, or null if its publicly accessible
user, api-key, notification-key, service Technical description for the technology, avoid marketing language
Documentation or readme url
Short one or two word name to show in places with limited space
If rejected, detail description of why
If rejected, the reason why
duplicate, incomplete, invalid, other Current status of the technology, including pending review, approved, and rejected. Approved technologies are visible to all users.
approved, pending-review, rejected Release notes or changelog url
Landing page website url
URL path name for the technology, used by stackfeed
user, api-key, notification-key, service Current and historical url path names used for the technology, used by stackfeed
Technology color used in diagrams
blue, green, yellow, orange, red, beaver, dark-blue, purple, pink, white, grey, black Icon that only works on dark backgrounds
Icon that only works on light backgrounds
Long verbose name
Service provider that provides this technology
aws, azure, gcp, microsoft, salesforce, atlassian, apache, supabase Restriction on which model object or connections this technology can be added to
actor, app, component, connection, group, store, system Type or category of technology
data-storage, deployment, framework-library, gateway, other, language, message-broker, network, protocol, runtime, service-tool user, api-key, notification-key, service Whether the technology is disabled and not visible to users
Use either iconUrlDark or iconUrlLight
Organization that owns this technology, or null if its publicly accessible
user, api-key, notification-key, service Technical description for the technology, avoid marketing language
Documentation or readme url
Short one or two word name to show in places with limited space
If rejected, detail description of why
If rejected, the reason why
duplicate, incomplete, invalid, other Current status of the technology, including pending review, approved, and rejected. Approved technologies are visible to all users.
approved, pending-review, rejected Release notes or changelog url
Landing page website url
URL path name for the technology, used by stackfeed
user, api-key, notification-key, service Current and historical url path names used for the technology, used by stackfeed
bug, calendar-check, calendar-times, cloud, cog, database, exclamation-triangle, file, globe, laptop-code, lightbulb, lock, microchip, minus, mobile, network-wired, plus, poo, robot, rocket, sack-dollar, server, sledding, snowman, star, times, toolbox, trash, users, wifi user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service blue, green, yellow, orange, red, beaver, dark-blue, purple, pink, white, grey, black user, api-key, notification-key, service user, api-key, notification-key, service user, api-key, notification-key, service 110user, api-key, notification-key, service user, api-key, notification-key, service