assign-offline-profile

1**Shared instructions: [shared-instructions.md](${PLUGIN_ROOT}/shared/shared-instructions.md)** — read first.
2 
3**References:**
4 
5- [offline-profile-schema.md](${PLUGIN_ROOT}/shared/references/offline-profile-schema.md) — `usermobileofflineprofilemembership` / `teammobileofflineprofilemembership` entity field map
6- [dataverse-offline-api.md](${PLUGIN_ROOT}/shared/references/dataverse-offline-api.md) — Web API recipe (§12 — membership POSTs)
7 
8# Assign Offline Profile
9 
10Bind one or more users and/or teams to an existing Mobile Offline Profile. Without this step, the profile exists in Dataverse but is unbound — no one's app actually uses it for offline sync.
11 
12Per the maker portal's UX (the "Assign profile to user" dialog under env settings), this is a separate operation from profile creation. Many users hit "I created the profile but offline still doesn't work" — the missing piece is membership.
13 
14Before project reads or commands, apply
15[app-working-directory.md](${PLUGIN_ROOT}/shared/references/app-working-directory.md).
16Resolve one absolute `working_dir` for a direct call or require the child
17invocation's owner root. Keep every shell/file operation, referenced recipe,
18and retry on that root and the selected environment/tenant; missing or
19conflicting context is `NEEDS_CONTEXT`. File tools use `<working_dir>/...`.
20Planning-phase calls may discover and propose the membership diff but must
21return before the confirmation gate, POST/DELETE, or artifact updates.
22 
23## Workflow
24…