Manage Users Setup Task Guidance
Purpose
Retain the CX Service Manage Users task identity while reusing all supported ResourceUser import, export, direct REST, membership, lifecycle, validation, and post-import use cases from CX Customer Data Management Manage Resources.
Setup Task Skill Contract
- task_code:
PER_MANAGE_USERS
- task_name:
Manage Users
- parent_skill_id:
cx.service.users-and-security
- pillar:
CX
- offering:
Service
- functional_area:
Users and Security
- functional_area_code:
ORA_ASK_USERS_AND_SECURITY
- available_flag:
Y
- export_import_supported_flag:
N
- csv_export_import_supported_flag:
N
- dataloader_import_mode:
CXIMPORT
- businessObject: ``
- source_catalog:
knowledge/setup-task-catalog/effective/setupTasksAll.json
Usage
Use this skill when a Service implementation objective is classified to Manage Users under Users and Security. Retain the task identity and reuse all supported
ResourceUser operation use cases from
cx.customer-data-management.resources.manage-resources.
Setup Task Metadata
- Task name:
Manage Users
- Task code:
PER_MANAGE_USERS
- Available:
Y
- Export/import supported:
N
- CSV export/import supported:
N
- CSV export/import routing:
not supported
- Data Loader import mode:
CXIMPORT
- Business Object: ``
Route To
Route to cx.customer-data-management.resources.manage-resources.
Use Cases
Resource User Import
Import one or more Resource Users through the CX Import workflow.
- Route the ResourceUser source and import context unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's Data Loader preview, validation envelope, approval, initiation, and explicit status workflow.
Resource User Import Status
Review the status, results, counts, or errors of an initiated ResourceUser import.
- Route the data-load request identity and status request unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's Data Loader status workflow; do not infer import completion.
Resource User Export
Export ResourceUser data through Export Management.
- Route the export name, filter, selected columns, output settings, activation choice, and download request unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's export preview, approval, activation, polling, and download workflow.
Resource User Get
Read one exact existing Resource User.
- Route the exact ResourceEmail or server-returned ResourcePartyNumber unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's exact identity resolution and authorized read contract.
Resource User Create
Create one Resource User through the documented direct REST workflow.
- Route the explicit direct-REST create request and required inputs unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's reference validation, immutable preview, approval, create, and verification workflow.
Resource User Update
Update one existing Resource User, including promotion, demotion, or transfer when supported by the source contract.
- Route the exact identity and requested minimal changes unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's exact-item read, preview, approval, PATCH, and verification workflow.
Resource User End Date
End-date one existing Resource User.
- Route the exact identity and requested ResourceEndDate unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's lifecycle review, preview, approval, PATCH, and verification workflow.
Direct Membership Add
Add an eligible Resource Organization membership for one Resource User.
- Route the binding membership handoff unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's role, organization, hierarchy, preview, approval, PATCH, and verification workflow.
Direct Membership Update
Update an eligible Resource Organization membership for one Resource User.
- Route the binding membership handoff unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's role, organization, hierarchy, preview, approval, PATCH, and verification workflow.
Direct Membership End Date
End-date an eligible Resource Organization membership for one Resource User.
- Route the binding membership handoff unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's role, organization, hierarchy, preview, approval, PATCH, and verification workflow.
Post Import Reporting Hierarchy Generation
Evaluate and route eligible Reporting Hierarchy Generation after a successful ResourceUser import.
- Route the successful import evidence and hierarchy context unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's post-import eligibility, structured handoff, preview, and separately approved execution workflow.
Post Import Send Pending Ldap Requests
Evaluate and route eligible Send Pending LDAP Requests processing after a successful ResourceUser import.
- Route the successful import evidence and LDAP context unchanged to cx.customer-data-management.resources.manage-resources.
- Use the receiving skill's post-import eligibility, preview, and separately approved execution workflow.
Resource User Delete
Permanently delete a Resource User.
Not supported. Resource Users DELETE is unsupported. Route the caller to resource end-date or organization-membership end-date instead; do not send a DELETE request.
Guard Rails
- Do not duplicate the Customer Data Management Manage Resources use cases or its ora-resource contracts in the Service overlay.
- Do not invoke core.data-loader, core.fusion-api.rest-api-client, or a Resource Users endpoint directly from Manage Users.
- Pass the original objective, project context, source artifacts, exact identity, export settings, and approval context unchanged to the receiving skill.
- Treat CX Import, Export Management, direct REST, post-import ESS, approval, retry, diagnostics, and verification behavior as owned by the receiving skill.
ResourceUser Operation Handoff
CSVExportImportSupportedFlag is N, so this task is not an FSM CSV
export/import route. ResourceUser operations reuse the separate, existing CX
Customer Data Management Manage Resources workflow as the authoritative
source of behavior and its task-local ora-resource/ contracts.
| Intent |
Handoff target |
| ResourceUser CX Import, import preview, initiation, status, results, and errors |
cx.customer-data-management.resources.manage-resources |
| ResourceUser Export Management creation, activation, polling, and download |
cx.customer-data-management.resources.manage-resources |
| Eligible post-import Reporting Hierarchy Generation and Send Pending LDAP Requests routing |
cx.customer-data-management.resources.manage-resources |
| One ResourceUser read, create, update, promotion, demotion, transfer, or end-date operation |
cx.customer-data-management.resources.manage-resources |
| Direct organization-membership add, update, or end-date operation |
cx.customer-data-management.resources.manage-resources |
| Resource role, organization, legal-entity, business-unit, person-type, and identity validation |
cx.customer-data-management.resources.manage-resources |
| Unsupported permanent ResourceUser deletion |
cx.customer-data-management.resources.manage-resources |
Pass the original implementation objective, project context, ResourceUser
operation, identity or source artifact, requested export settings, and approval
context unchanged. The receiving skill owns current and future supported
ResourceUser use cases, reference lookups, input and dependency validation,
Data Loader or REST route selection, immutable previews, approval gates,
diagnostics, and project execution records.
Do not invoke core.data-loader, core.fusion-api.rest-api-client, or a
Resource Users endpoint directly from this task. Do not duplicate the receiving
skill's ResourceUser contracts or infer an alternate route.
Reused Resource Contracts
This Service overlay has no task-local ora-resource/ package. Use the
authoritative resource contracts in
cx.customer-data-management.resources.manage-resources,
including its complete ora-resource/ package, for every routed operation.
Inputs
implementation_objective
project_context
setup_task_scope
setup_data_artifacts
Outputs
setup_task_plan
setup_data_routing
validation_checkpoints
resource_management_handoff
skill_run_record
token_usage_record
Implementation Notes
Use the parent functional-area skill cx.service.users-and-security for
functional-area sequencing and scope decisions. Track token usage for any
generated project artifact or skill-run record using the manifest policy.
1---2skill_id: "cx.service.users-and-security.manage-users"3name: manage-users-setup-task-guidance4description: "Provides task-specific setup guidance for Manage Users under the Users and Security functional area."5layer: "pillar"6pillar: "CX"7offering: "Service"8functional_area: "Users and Security"9functional_area_code: "ORA_ASK_USERS_AND_SECURITY"10task_code: "PER_MANAGE_USERS"11task_name: "Manage Users"12parent_skill_id: "cx.service.users-and-security"13available_flag: "Y"14export_import_supported_flag: "N"15csv_export_import_supported_flag: "N"16dataloader_import_mode: "CXIMPORT"17businessObject: ""18source_catalog: "knowledge/setup-task-catalog/effective/setupTasksAll.json"19type: "planning"20execution_mode: "assisted"21owner_team: "CX service pillar team"22version: "0.1.0"23inputs:24 - "implementation_objective"25 - "project_context"26 - "setup_task_scope"27 - "setup_data_artifacts"28outputs:29 - "setup_task_plan"30 - "setup_data_routing"31 - "validation_checkpoints"32 - "skill_run_record"33 - "token_usage_record"34uses_core:35 - "core.project-mgmt.artifact-version-manager"36 - "core.project-mgmt.artifact-registry-manager"37 - "core.project-mgmt.project-state-manager"38persists_project_state: true39token_usage_tracking:40 enabled: true41 granularity: "per_skill_run"42 artifact_type: "token_usage_record"43 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"44 estimation_method: "chars/4 estimate unless exact tokenizer or API accounting is available"45 required_fields:46 - "activity_start_time"47 - "skill_id"48 - "task"49 - "trigger"50 - "artifacts_written"51 - "files_read"52 - "estimated_input_tokens"53 - "estimated_output_tokens"54 - "estimated_total_tokens"55 - "estimation_method"56 - "notes"57state_updates:58 - "setup_task_sequence"59 - "configuration_blueprints"60 - "validation_results"61 - "token_usage_records"62workspace_outputs:63 - artifact_type: "configuration_blueprint"64 default_location: "project/{project_id}/artifacts/pillars/cx/service/users-and-security/manage-users/current/"65 versioning_policy: "major-new-version-minor-confirm-update"66 - artifact_type: "validation_result"67 default_location: "project/{project_id}/artifacts/pillars/cx/service/users-and-security/manage-users/current/"68 versioning_policy: "major-new-version-minor-confirm-update"69 - artifact_type: "skill_run"70 default_location: "project/{project_id}/state/runs/"71 versioning_policy: "append-only"72 - artifact_type: "token_usage_record"73 default_location: "project/{project_id}/artifacts/shared/token-usage/current/token-usage-log.md"74 versioning_policy: "append-only"75applicability:76 industries:77 - "All"78 countries:79 - "All"80 fusion_releases:81 - "Current Oracle Fusion Cloud release"82side_effects: []83required_privileges: []84depends_on:85 - "cx.customer-data-management.resources.manage-resources"86metadata:87 source: https://skillmd.com/skills/oracle/manage-users-setup-task-guidance88---8990# Manage Users Setup Task Guidance9192## Purpose9394Retain the CX Service Manage Users task identity while reusing all supported ResourceUser import, export, direct REST, membership, lifecycle, validation, and post-import use cases from CX Customer Data Management Manage Resources.95## Setup Task Skill Contract9697- task_code: `PER_MANAGE_USERS`98- task_name: `Manage Users`99- parent_skill_id: `cx.service.users-and-security`100- pillar: `CX`101- offering: `Service`102- functional_area: `Users and Security`103- functional_area_code: `ORA_ASK_USERS_AND_SECURITY`104- available_flag: `Y`105- export_import_supported_flag: `N`106- csv_export_import_supported_flag: `N`107- dataloader_import_mode: `CXIMPORT`108- businessObject: ``109- source_catalog: `knowledge/setup-task-catalog/effective/setupTasksAll.json`110111## Usage112113Use this skill when a Service implementation objective is classified to `Manage114Users` under `Users and Security`. Retain the task identity and reuse all supported115ResourceUser operation use cases from116`cx.customer-data-management.resources.manage-resources`.117118## Setup Task Metadata119120- Task name: `Manage Users`121- Task code: `PER_MANAGE_USERS`122- Available: `Y`123- Export/import supported: `N`124- CSV export/import supported: `N`125- CSV export/import routing: `not supported`126- Data Loader import mode: `CXIMPORT`127- Business Object: ``128129130131132## Route To133134Route to cx.customer-data-management.resources.manage-resources.135## Use Cases136137### Resource User Import138139Import one or more Resource Users through the CX Import workflow.1401411. Route the ResourceUser source and import context unchanged to cx.customer-data-management.resources.manage-resources.1422. Use the receiving skill's Data Loader preview, validation envelope, approval, initiation, and explicit status workflow.143144### Resource User Import Status145146Review the status, results, counts, or errors of an initiated ResourceUser import.1471481. Route the data-load request identity and status request unchanged to cx.customer-data-management.resources.manage-resources.1492. Use the receiving skill's Data Loader status workflow; do not infer import completion.150151### Resource User Export152153Export ResourceUser data through Export Management.1541551. Route the export name, filter, selected columns, output settings, activation choice, and download request unchanged to cx.customer-data-management.resources.manage-resources.1562. Use the receiving skill's export preview, approval, activation, polling, and download workflow.157158### Resource User Get159160Read one exact existing Resource User.1611621. Route the exact ResourceEmail or server-returned ResourcePartyNumber unchanged to cx.customer-data-management.resources.manage-resources.1632. Use the receiving skill's exact identity resolution and authorized read contract.164165### Resource User Create166167Create one Resource User through the documented direct REST workflow.1681691. Route the explicit direct-REST create request and required inputs unchanged to cx.customer-data-management.resources.manage-resources.1702. Use the receiving skill's reference validation, immutable preview, approval, create, and verification workflow.171172### Resource User Update173174Update one existing Resource User, including promotion, demotion, or transfer when supported by the source contract.1751761. Route the exact identity and requested minimal changes unchanged to cx.customer-data-management.resources.manage-resources.1772. Use the receiving skill's exact-item read, preview, approval, PATCH, and verification workflow.178179### Resource User End Date180181End-date one existing Resource User.1821831. Route the exact identity and requested ResourceEndDate unchanged to cx.customer-data-management.resources.manage-resources.1842. Use the receiving skill's lifecycle review, preview, approval, PATCH, and verification workflow.185186### Direct Membership Add187188Add an eligible Resource Organization membership for one Resource User.1891901. Route the binding membership handoff unchanged to cx.customer-data-management.resources.manage-resources.1912. Use the receiving skill's role, organization, hierarchy, preview, approval, PATCH, and verification workflow.192193### Direct Membership Update194195Update an eligible Resource Organization membership for one Resource User.1961971. Route the binding membership handoff unchanged to cx.customer-data-management.resources.manage-resources.1982. Use the receiving skill's role, organization, hierarchy, preview, approval, PATCH, and verification workflow.199200### Direct Membership End Date201202End-date an eligible Resource Organization membership for one Resource User.2032041. Route the binding membership handoff unchanged to cx.customer-data-management.resources.manage-resources.2052. Use the receiving skill's role, organization, hierarchy, preview, approval, PATCH, and verification workflow.206207### Post Import Reporting Hierarchy Generation208209Evaluate and route eligible Reporting Hierarchy Generation after a successful ResourceUser import.2102111. Route the successful import evidence and hierarchy context unchanged to cx.customer-data-management.resources.manage-resources.2122. Use the receiving skill's post-import eligibility, structured handoff, preview, and separately approved execution workflow.213214### Post Import Send Pending Ldap Requests215216Evaluate and route eligible Send Pending LDAP Requests processing after a successful ResourceUser import.2172181. Route the successful import evidence and LDAP context unchanged to cx.customer-data-management.resources.manage-resources.2192. Use the receiving skill's post-import eligibility, preview, and separately approved execution workflow.220221### Resource User Delete222223Permanently delete a Resource User.224225Not supported. Resource Users DELETE is unsupported. Route the caller to resource end-date or organization-membership end-date instead; do not send a DELETE request.226## Guard Rails2272281. Do not duplicate the Customer Data Management Manage Resources use cases or its ora-resource contracts in the Service overlay.2292. Do not invoke core.data-loader, core.fusion-api.rest-api-client, or a Resource Users endpoint directly from Manage Users.2303. Pass the original objective, project context, source artifacts, exact identity, export settings, and approval context unchanged to the receiving skill.2314. Treat CX Import, Export Management, direct REST, post-import ESS, approval, retry, diagnostics, and verification behavior as owned by the receiving skill.232## ResourceUser Operation Handoff233234`CSVExportImportSupportedFlag` is `N`, so this task is not an FSM CSV235export/import route. ResourceUser operations reuse the separate, existing CX236Customer Data Management `Manage Resources` workflow as the authoritative237source of behavior and its task-local `ora-resource/` contracts.238239| Intent | Handoff target |240|---|---|241| ResourceUser CX Import, import preview, initiation, status, results, and errors | `cx.customer-data-management.resources.manage-resources` |242| ResourceUser Export Management creation, activation, polling, and download | `cx.customer-data-management.resources.manage-resources` |243| Eligible post-import Reporting Hierarchy Generation and Send Pending LDAP Requests routing | `cx.customer-data-management.resources.manage-resources` |244| One ResourceUser read, create, update, promotion, demotion, transfer, or end-date operation | `cx.customer-data-management.resources.manage-resources` |245| Direct organization-membership add, update, or end-date operation | `cx.customer-data-management.resources.manage-resources` |246| Resource role, organization, legal-entity, business-unit, person-type, and identity validation | `cx.customer-data-management.resources.manage-resources` |247| Unsupported permanent ResourceUser deletion | `cx.customer-data-management.resources.manage-resources` |248249Pass the original implementation objective, project context, ResourceUser250operation, identity or source artifact, requested export settings, and approval251context unchanged. The receiving skill owns current and future supported252ResourceUser use cases, reference lookups, input and dependency validation,253Data Loader or REST route selection, immutable previews, approval gates,254diagnostics, and project execution records.255256Do not invoke `core.data-loader`, `core.fusion-api.rest-api-client`, or a257Resource Users endpoint directly from this task. Do not duplicate the receiving258skill's ResourceUser contracts or infer an alternate route.259260## Reused Resource Contracts261262This Service overlay has no task-local `ora-resource/` package. Use the263authoritative resource contracts in264[`cx.customer-data-management.resources.manage-resources`](../../../customer-data-management/resources/manage-resources/SKILL.md),265including its complete `ora-resource/` package, for every routed operation.266267268269## Inputs270271- `implementation_objective`272- `project_context`273- `setup_task_scope`274- `setup_data_artifacts`275276## Outputs277278- `setup_task_plan`279- `setup_data_routing`280- `validation_checkpoints`281- `resource_management_handoff`282- `skill_run_record`283- `token_usage_record`284285## Implementation Notes286287Use the parent functional-area skill `cx.service.users-and-security` for288functional-area sequencing and scope decisions. Track token usage for any289generated project artifact or skill-run record using the manifest policy.