slug: retool provider: Retool generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Software & Technology min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 3 edges: - tag: Users spec_file: retool-users-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.8 evidence: POST /users createUser Create User; DELETE /users/{userId} deleteUser Delete User; 'supports SCIM 2.0 for enterprise identity provider provisioning via Okta and Azure AD' reason: Full user lifecycle CRUD plus SCIM provisioning for an organisation's platform accounts is identity and access management (joiners-movers-leavers), not HR records. - tag: Apps spec_file: retool-apps-api-openapi.yml capability_id: BC-600.60 capability_id_l1: BC-600 capability_name: IT Application Management confidence: 0.75 evidence: The Retool Management API enables administrators to programmatically manage users, groups, permissions, apps, resources... ; POST /apps createApp reason: CRUD over internal-tool applications in a low-code platform is IT application lifecycle management for the buying organisation. - tag: Groups spec_file: retool-groups-api-openapi.yml capability_id: BC-620.20 capability_id_l1: BC-620 capability_name: Identity & Access Management confidence: 0.75 evidence: 'POST /groups/{groupId}/members addGroupMember Add Member to Group; description: ''programmatically manage users, groups, permissions''' reason: Group creation and membership management is the access-control grouping mechanism for the Retool organisation, i.e. identity and access administration. Some ambiguity since groups could also be read as mere collaboration structures, hence moderate confidence.