@lotics/cli 0.321.22 → 0.321.23
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/AGENTS.md +1 -1
- package/README.md +3 -3
- package/dist/src/cli.js +14 -14
- package/docs/agent_surface.md +1 -1
- package/docs/app_architecture.md +1 -1
- package/docs/cli_reference.md +6 -6
- package/docs/permissions.md +24 -11
- package/docs/workflow_steps.md +2 -2
- package/docs/working_in_a_workspace.md +4 -4
- package/package.json +1 -1
package/docs/agent_surface.md
CHANGED
|
@@ -182,7 +182,7 @@ run_app_workflow {"app_id":"app_…","alias":"act_hand_over","inputs":{"record_i
|
|
|
182
182
|
|---|---|
|
|
183
183
|
| `inputs` | The workflow's declared inputs. An update takes the record and only the fields that change |
|
|
184
184
|
| `dry_run` | `true`: the run is made and taken back, so nothing is kept, and the answer is what the run would return, with the calls it would make — or `status: "not_previewed"` where the workflow cannot be dry-run (`agent_surface/a-dry-run`) |
|
|
185
|
-
| `as_member` | For
|
|
185
|
+
| `as_member` | For an organization owner: the run is a dry run, judged as that member would press it — their stage owners, row rules and app access — and writes nothing. Anyone else is refused; a record tool takes it the same way, and so do `query_records` and `run_app_query`, which answer what that member would read, and `screenshot_app`, which draws the app as that member sees it |
|
|
186
186
|
| `runs` | Several runs in one call, 50 at most, in order, each its own write, answered under `runs`. The first one refused, failed or not dry-run ends the call. An input `{"from_run": 0, "path": "data.record_id"}` is an earlier run's answer at that path. A run states its own `dry_run`, or takes the call's. Dry runs one after another share their rows, taken back together, so a run reads what the one before it made; a run reads a dry run's answer only from a run dry-run in that stretch |
|
|
187
187
|
|
|
188
188
|
```
|
package/docs/app_architecture.md
CHANGED
|
@@ -32,7 +32,7 @@ How each tree is composed is `design`.
|
|
|
32
32
|
|
|
33
33
|
## Who gets each
|
|
34
34
|
|
|
35
|
-
Who does which job is asked in `build`'s one message before the first write. An app stays with admins until the answer comes, and sharing waits on it. `set_access` then gives each app to everyone who works its rows (ids from `get_workspace`); none loses access. They need no
|
|
35
|
+
Who does which job is asked in `build`'s one message before the first write. An app stays with admins until the answer comes, and sharing waits on it. `set_access` then gives each app to everyone who works its rows (ids from `get_workspace` kind `member`, which lists the people in this workspace); none loses access. Someone who works its rows and is not in the workspace is added first by an organization owner (`set_members`, `role: "member"`), since a share reaches only people in the workspace. They need no
|
|
36
36
|
table access: an app runs as its owner. With no `rows` on the App they read every row; where people differ, `rows`
|
|
37
37
|
states one rule per table (`reference/read-scope`):
|
|
38
38
|
|
package/docs/cli_reference.md
CHANGED
|
@@ -19,11 +19,11 @@ Per-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. S
|
|
|
19
19
|
| `lotics org use <name\|id> [--local]` | Switch the active org by org name (case-insensitive, ambiguous → error) or id. No flag → global `active_org`; `--local` → a `.lotics/config.json` pointer in the current dir. |
|
|
20
20
|
| `lotics workspace` | List workspaces in the active org, marks current with `(current)` |
|
|
21
21
|
| `lotics workspace select <id>` | Set the workspace in the **active scope** — a local pin if the dir has one, else the active org's global profile. Records the workspace's NAME beside its id, which is what the `lotics → <org> / <workspace>` echo prints; `workspace list`, `workspace create`, `workspace rename` and `org use` record it too, so a target is named rather than identified. Until one command has listed it, the echo prints the id and says the name is not known yet. |
|
|
22
|
-
| `lotics workspace create <name> [--timezone <Area/City>] [--currency <ISO>]` | Create a new workspace (
|
|
23
|
-
| `lotics workspace rename <name>` | Rename the **current** workspace (admin only) — the endpoint takes its target from the request's workspace, never a path id, so switch with `workspace select <id>` first and read the `lotics → <org> / <workspace>` echo before trusting it — both halves are names, and the rename moves the cached one in the same act. Carries the workspace's existing `default_currency` and `timezone` through unchanged: the endpoint takes the whole settings triple, so sending only a name would blank the other two. |
|
|
24
|
-
| `lotics workspace settings [--name <n>] [--currency <ISO>] [--timezone <Area/City>]` | Change the CURRENT workspace's name, default currency or timezone — `PATCH /v1/workspace`, admin only. Only what you name changes; the endpoint takes the whole triple, so the CLI carries the two you did not. `rename` is this verb with the name alone, which is why it can never forget the other two. Both values are invisible once they are wrong: the currency decides how every money field RENDERS and the zone decides how every date BUCKETS, on a workspace whose whole purpose may be to look like the customer's own. `--json` prints the updated workspace. |
|
|
25
|
-
| `lotics workspace delete <id> --yes` | Delete a workspace by id (
|
|
26
|
-
| `lotics workspace doctor` | Report workspace-wide dangling schema references via `GET /v1/workspaces/dangling-references` — every active app/workflow artifact whose prefixed schema id no longer resolves, printed as `<referent.kind> "<name>" (<id>) → <namespace> <id> (missing)`; healthy prints a one-line all-clear. **Exits non-zero (exit 1) on findings** so scripts can gate on it. Resolves the first workspace like every data command (runs before the global workspace resolution). Admin-only. |
|
|
22
|
+
| `lotics workspace create <name> [--timezone <Area/City>] [--currency <ISO>]` | Create a new workspace (organization owner only), auto-switches to it. Neither flag is defaulted from THIS machine, unlike signup: an extra workspace is routinely created by an operator for somebody else. Without `--timezone` the new workspace inherits the zone of the org's OLDEST workspace; without `--currency` it takes the org's default. Both ride the create, so the workspace is never briefly denominated in a currency nobody asked for. `--currency` takes an ISO-4217 code (case-insensitive; anything else is refused). |
|
|
23
|
+
| `lotics workspace rename <name>` | Rename the **current** workspace (an admin of that workspace only) — the endpoint takes its target from the request's workspace, never a path id, so switch with `workspace select <id>` first and read the `lotics → <org> / <workspace>` echo before trusting it — both halves are names, and the rename moves the cached one in the same act. Carries the workspace's existing `default_currency` and `timezone` through unchanged: the endpoint takes the whole settings triple, so sending only a name would blank the other two. |
|
|
24
|
+
| `lotics workspace settings [--name <n>] [--currency <ISO>] [--timezone <Area/City>]` | Change the CURRENT workspace's name, default currency or timezone — `PATCH /v1/workspace`, an admin of that workspace only. Only what you name changes; the endpoint takes the whole triple, so the CLI carries the two you did not. `rename` is this verb with the name alone, which is why it can never forget the other two. Both values are invisible once they are wrong: the currency decides how every money field RENDERS and the zone decides how every date BUCKETS, on a workspace whose whole purpose may be to look like the customer's own. `--json` prints the updated workspace. |
|
|
25
|
+
| `lotics workspace delete <id> --yes` | Delete a workspace by id (organization owner only). **Soft delete** — `archived_at` is set, so it drops out of listings, can no longer be selected, and its tables/records go dark, while the data is retained and recoverable. Its **apps are cascade-archived** too — every app entry point (embedded, public link, standalone subdomain, incl. anonymous public links) stops serving. Refuses the org's **only** active workspace (400) and any workspace outside the caller's org (404). Requires `--yes` to confirm (destructive; the CLI is used non-interactively). |
|
|
26
|
+
| `lotics workspace doctor` | An admin of that workspace only. Report workspace-wide dangling schema references via `GET /v1/workspaces/dangling-references` — every active app/workflow artifact whose prefixed schema id no longer resolves, printed as `<referent.kind> "<name>" (<id>) → <namespace> <id> (missing)`; healthy prints a one-line all-clear. **Exits non-zero (exit 1) on findings** so scripts can gate on it. Resolves the first workspace like every data command (runs before the global workspace resolution). Admin-only. |
|
|
27
27
|
| `lotics tools` | List tools by category with descriptions |
|
|
28
28
|
| `lotics tools <name>` | Full description, input JSON Schema, and the output schema where the tool answers a shape, for one tool; a workflow step says to call it from a workflow body, not `lotics run` |
|
|
29
29
|
| `lotics run <tool> '<json>'` | Execute a tool (text output via toModelOutput). Args may also come from a file (`lotics run <tool> @args.json`) or stdin behind the `-` sentinel (`cat args.json \| lotics run <tool> -`) — both bypass the OS `ARG_MAX` limit for large payloads (a knowledge-doc `content`, a bulk update). A leading `@` on the args is unambiguously a file path (JSON args start with `{`). **Stdin is asked for, never guessed.** `lotics run <tool>` with no payload runs the tool with no arguments and returns at once. `lotics report` takes the same sentinel. In PowerShell use `@file`: quotes inside an inline argument are consumed by the shell, and the CLI reports the JSON it received with its quotes gone — the error names both escapes. |
|
|
@@ -33,7 +33,7 @@ Per-command syntax, flags, contracts, and gotchas for the public `lotics` CLI. S
|
|
|
33
33
|
| — | **An app's queries and workflows take more than their params and inputs** (`lotics docs agent_surface`). `run_app_query '{"app_id","alias","params"}'` also takes `filters` and `sort` over the query's output columns, `fields` (the columns to return), `count` with `count_by` or `count_where`, `aggregate`, `limit` (200 rows at most; 50 where none is stated) and `cursor`, and `runs` — up to 20 reads in one call, each `{"alias", …}`, a refused one answered with its `error`; one call's rows total at most 262,144 bytes. `export: {"key", …narrowing}` instead of the read arguments makes the file an app's Export makes (`lotics docs agent_surface`). `run_app_workflow '{"app_id","alias","inputs"}'` also takes `dry_run: true` — a rehearsal on the real inputs, nothing written or sent; the answer is what the run would return, with the reads it made under `dry_run.reads`, the calls it would make under `dry_run.writes` and the papers it rendered under `dry_run.papers` and the parts of the answer it could not say under `dry_run.unpredicted`; a workflow no dry run is offered of answers `status: "not_previewed"` — and `runs` — up to 50 runs in order, the first refused, failed or not previewed ending the call, an input `{"from_run": <index>, "path": "data.<key>"}` reading an earlier run's answer. |
|
|
34
34
|
| — | **The exit code reports the WORK, not just the call — for the tool that RUNS one.** `run_app_workflow` whose envelope carries a failed `status` (`error`/`failed`/`cancelled`, or `not_previewed` — a dry run asked for and not given) exit non-zero and print `<tool> → <status>: <message>` to stderr, so `lotics run … && next-step` cannot walk past a refused run. The rule is an allowlist of FAILURE — an unrecognized status exits 0, so a status added later never turns a working script red. A parked run (`awaiting_input`) is not a failure: it is waiting for an answer and the work is still live. Only a TOP-LEVEL `status` counts; one inside the data belongs to the data. Any OTHER tool's `status` is data, and exits 0. |
|
|
35
35
|
| `lotics run <tool> '<json>' -o <dir>` | Also save every **signed link** the answer carries — an object with a `url`, a `filename` and the `expires_at` its signature ends at, at any depth, such as `screenshot_app`'s images. Each is fetched into `<dir>` (created if missing) under its `filename`, taking a free spelling beside a file of that name already there, and a link's `snapshot` text is written beside it as `<name>.txt`. The written paths follow the answer on **stdout**, one per line (on stderr under `--json`, whose stdout stays the one object). A link is signed for an hour; one the store no longer serves exits non-zero. A workspace file states no `expires_at` and is left to `lotics file download`. |
|
|
36
|
-
| `lotics run set_members '{"members": {"<email or member id>": {"role": "member", "name": "…"}}}'` | Invite, rename,
|
|
36
|
+
| `lotics run set_members '{"members": {"<email or member id>": {"role": "member", "name": "…"}}}'` | Invite to this workspace, rename, set the role in this workspace (`role`: `member` or `admin`; `null` takes the person out of it), set the organization role (`organization_role`: `co_owner` or `member`, the primary owner's), remove from the organization (`remove: true`) or restore members; `groups` keeps the member groups in the same call. Organization owner only: the whole input is checked before an email is sent. A workspace admin's `lotics tools` lists `set_workspace` and not `set_members`; a member's lists neither. View-as is the web app's preview alone; the CLI acts as the signed-in member. |
|
|
37
37
|
| `lotics run <tool> --print-created` | Report the records the call created, grouped by table, with a paste-ready `delete_records` per table and the mandatory caveat naming what cannot be auto-undone (external integrations, notifications, possible sub-workflows). Works for any tool that returns a `side_effects` block, not workflows alone. |
|
|
38
38
|
| `lotics run <tool> --cleanup` | Implies `--print-created`, then runs those deletes — harvested records **only**, never files / external calls / notifications. **Not a rollback**; a rollback is structurally impossible here. A partial cleanup exits non-zero so a script cannot read it as success. |
|
|
39
39
|
| `lotics file upload <file\|dir...>` (alias `lotics upload`) · `--stdin` · `--base64` · `--url <url>` | Upload files/directories. **The transport is chosen by size and is not a flag**: under 8 MiB the file is POSTed to `/v1/files`, several such files to a request up to half that route's 100 MiB cap; at or above it the CLI takes presigned part URLs and PUTs the bytes straight to object storage, so they never pass through the API. That threshold matches the AWS CLI's own `multipart_threshold`, and the number matters less than there being nothing to choose — one verb, any size, up to the 2 GiB a workspace may store. A large upload reads one part at a time, so memory stays flat regardless of file size, and a failure part-way abandons the parts already sent rather than leaving them billable and invisible. A directory expands to its immediate files; `--as <name>` renames a single upload. **Three alternative byte sources, for a caller that never had the bytes on disk** — an attachment decoded in memory, a generated document, a signed download link — each mutually exclusive with the others and with a path argument: `--stdin` takes raw bytes on stdin, `--base64` takes base64 on stdin (the shape attachments arrive in), `--url <url>` fetches the URL first. `--stdin`/`--base64` REQUIRE `--as`, because stdin carries no filename and the mime type is derived from it; `--url` falls back to `Content-Disposition` then the URL's last path segment. `--base64` decodes STRICTLY — `Buffer.from(s, "base64")` silently skips invalid characters and truncates on bad padding, so a corrupted pipe would otherwise store a short file that only fails when a human opens it. The `--url` fetch happens in the CLI, not the server: the URL comes from the operator running the command, so routing it through the backend would add an SSRF surface to buy what `curl` already does. |
|
package/docs/permissions.md
CHANGED
|
@@ -6,22 +6,34 @@ Who can reach what, what runs under whose access, and what a refusal means.
|
|
|
6
6
|
|
|
7
7
|
An agent over MCP, or a terminal signed in with `lotics auth login`, acts as the member who approved it: it reaches
|
|
8
8
|
what that member reaches, and no more. An `ltk_` key set to **Only selected ones** is its own narrow member: it reaches
|
|
9
|
-
the apps and tables named on it, and a share to
|
|
10
|
-
tables** reaches the organization. `get_workspace` lists what the caller can use.
|
|
9
|
+
the apps and tables named on it, and a share to everyone in a workspace does not reach it. A key set to **All apps and
|
|
10
|
+
tables** reaches every workspace of the organization. `get_workspace` lists what the caller can use.
|
|
11
|
+
|
|
12
|
+
## Who is in a workspace
|
|
13
|
+
|
|
14
|
+
A person is in a workspace only when added to it, as its **admin** or a **member**. Ownership and shares grant only
|
|
15
|
+
inside a workspace the person is in. **Organization owners** — the primary owner and co-owners — are admin of every
|
|
16
|
+
workspace and alone manage people, invitations, groups, API keys, the access log, billing, usage, workspaces and the
|
|
17
|
+
organization's settings; only the primary owner makes or unmakes a co-owner. A workspace admin holds everything else in
|
|
18
|
+
their workspace: its settings and instructions, sharing, apps and publishing them, tables, templates, docs, workflows,
|
|
19
|
+
connections and restores. `get_workspace` kind `member` lists the people in this workspace; an organization owner passes
|
|
20
|
+
`all: true` for the whole organization. `set_members` adds a person to the workspace (`working_in_a_workspace`).
|
|
11
21
|
|
|
12
22
|
## Ownership and sharing
|
|
13
23
|
|
|
14
24
|
Every table, app, knowledge doc, document template, skill, automation, notification workflow and connection has one
|
|
15
|
-
owner. Everything starts private, and sharing is the only way to widen it. `set_access` gives a member
|
|
16
|
-
|
|
25
|
+
owner. Everything starts private, and sharing is the only way to widen it. `set_access` gives a member or a group in the
|
|
26
|
+
workspace, or everyone in it, a role on a resource (`working_in_a_workspace`). A share with someone outside the workspace,
|
|
27
|
+
or with a group holding anyone outside it, is refused: the person is added to the workspace first, by an organization owner with `set_members`. Several shares add up, the highest role wins, and
|
|
17
28
|
there is no deny.
|
|
18
29
|
|
|
19
30
|
**Lists are shorter than reach.** A listing shows your own work and what is shared with you. An admin's listing says what it left out (`not_listed`), and `all: true` on `get_workspace` lists it: apps, knowledge docs and templates. An admin's agent lists every table, automation and connection without it. A doc search covers what is listed, so a member's private doc enters an admin's answers only with `all: true`. By id, an admin reaches anything. Sharing an item with yourself through `set_access` lists it from then on.
|
|
20
31
|
|
|
21
32
|
| Role | Reaches |
|
|
22
33
|
|---|---|
|
|
23
|
-
| Organization owner
|
|
24
|
-
|
|
|
34
|
+
| Organization owner | Every resource of every workspace |
|
|
35
|
+
| Workspace admin | Every resource of that workspace |
|
|
36
|
+
| Member | What they own and what is shared with them, in the workspaces they are in |
|
|
25
37
|
|
|
26
38
|
## Two doors to data
|
|
27
39
|
|
|
@@ -50,16 +62,17 @@ and a person who owns the target or an admin can share it with them as viewer.
|
|
|
50
62
|
## What runs, runs as its owner
|
|
51
63
|
|
|
52
64
|
A workflow, app, automation and notification workflow uses its owner's current permissions. Pressing a button, answering
|
|
53
|
-
a card or filling a form only triggers it. If the owner loses access, the run fails. Only the owner or an admin writes a
|
|
65
|
+
a card or filling a form only triggers it. If the owner loses access, the run fails; if the owner is not in the workspace, it is refused before any step and the workspace's admins are told. Only the owner or an admin writes a
|
|
54
66
|
body, and that includes a notification workflow and naming it on a card; it still runs as its owner.
|
|
55
67
|
|
|
56
|
-
Saving a body needs its owner to be able to use every connection, template and knowledge doc it names. To inspect what a member would get, an
|
|
68
|
+
Saving a body needs its owner to be able to use every connection, template and knowledge doc it names. To inspect what a member would get, an organization owner passes `as_member` with a read or a dry run.
|
|
57
69
|
|
|
58
70
|
## Connections
|
|
59
71
|
|
|
60
|
-
A connection belongs to the
|
|
61
|
-
whoever it is shared with can act through it, and
|
|
62
|
-
to another keeps its shares; any other
|
|
72
|
+
A connection belongs to the organization and sits in one workspace. Only an admin of it connects one, in Lotics under
|
|
73
|
+
Settings → Connections. Its admins and whoever it is shared with can act through it, and when its owner leaves it passes
|
|
74
|
+
on with their other resources. An app handed from one admin of its workspace to another keeps its shares; any other
|
|
75
|
+
handover clears them.
|
|
63
76
|
|
|
64
77
|
A workflow step's `connected_account_id` is a literal, a constant bound to one, or a choice among them, so every possible
|
|
65
78
|
value is judged at save; one read from an input, a record or a call is refused at save and at run. A document template
|
package/docs/workflow_steps.md
CHANGED
|
@@ -38,7 +38,7 @@ above. A provider's refusal carries the provider's own words.
|
|
|
38
38
|
| Name | Type | Required | What it is |
|
|
39
39
|
| --- | --- | --- | --- |
|
|
40
40
|
| `table_id` | string | yes | |
|
|
41
|
-
| `as_member` | string | | For
|
|
41
|
+
| `as_member` | string | | For an organization owner: reads as this member would — their row rules and access. Anyone else is refused. |
|
|
42
42
|
| `filters` | any | | |
|
|
43
43
|
| `aggregate_option` | any | | |
|
|
44
44
|
| `aggregations` | any[] | | At most 25 entries. |
|
|
@@ -2165,7 +2165,7 @@ above. A provider's refusal carries the provider's own words.
|
|
|
2165
2165
|
| --- | --- | --- | --- |
|
|
2166
2166
|
| `record_id` | string | yes | |
|
|
2167
2167
|
| `table_id` | string | | |
|
|
2168
|
-
| `as_member` | string | | For
|
|
2168
|
+
| `as_member` | string | | For an organization owner: reads as this member would — their row rules and access. Anyone else is refused. |
|
|
2169
2169
|
| `field_keys` | string[] | | Field aliases to return. Omit to return all fields. |
|
|
2170
2170
|
| `comments` | boolean | | Return the record's newest comments, 20 at most; `comment_count` is the whole thread. |
|
|
2171
2171
|
|
|
@@ -17,15 +17,15 @@ Find the means in this order: `get_workspace` maps the workspace; `search` it by
|
|
|
17
17
|
|
|
18
18
|
## Workspace settings and standing instructions
|
|
19
19
|
|
|
20
|
-
`get_workspace` shows the workspace's settings (name, timezone, default currency) and, with kind `instruction`, its standing instructions. `set_workspace` changes them in one all-or-nothing patch: a setting it leaves out is unchanged, and `instructions` is a map keyed by instruction name where an entry creates or merges and `null` removes. A workspace-wide instruction arrives with the connection, in the instructions a host reads when an agent connects; the answer of `set_workspace` names any that no longer fit that block. An
|
|
20
|
+
`get_workspace` shows the workspace's settings (name, timezone, default currency) and, with kind `instruction`, its standing instructions. `set_workspace` changes them in one all-or-nothing patch: a setting it leaves out is unchanged, and `instructions` is a map keyed by instruction name where an entry creates or merges and `null` removes. A workspace-wide instruction arrives with the connection, in the instructions a host reads when an agent connects; the answer of `set_workspace` names any that no longer fit that block. An admin of the workspace writes the settings, the instructions and the workspace's and its apps' credit limits; the organization's name and language and a member's credit limit are an organization owner's, and a call stating one without being one is refused naming which.
|
|
21
21
|
|
|
22
22
|
## People
|
|
23
23
|
|
|
24
|
-
`get_workspace` with kind `member` lists
|
|
24
|
+
`get_workspace` with kind `member` lists the name and id of each person in this workspace; an organization owner passes `all: true` for everyone in the organization. An admin of the workspace also sees each one's email, organization `role`, `workspace_role` (`admin`, `member`, or null for a person outside it), `managed` and `sign_in_name`, and, on kind `app`, `knowledge` or `template`, `not_listed`: how many more they can reach, which `all: true` lists. Listed docs and templates carry `access`. An admin also reads the credit limits there. With kind `group`, an organization owner lists every group and anyone else the groups whose whole roster is in this workspace.
|
|
25
25
|
|
|
26
|
-
`set_members` is an
|
|
26
|
+
`set_members` is an organization owner's: `members` is a map keyed by an email address, a member id or a managed member's sign-in name, and `groups` a map keyed by a group id, or by a group's name, which sets the group of that name or creates it (refused where several groups share it: key that entry by id). In `members`, `role` is the person's role in THIS workspace, `member` or `admin`; `role: null` takes them out of it, ending their shares here and passing what they own here to the caller. An email no member holds invites that person to the organization as a member, with `role` as their place here (`member` when omitted; the invitation email goes out). A current member's entry sets `name`, `role`, and `organization_role`: `co_owner` or `member`, which only the primary owner sets; a co-owner made a member passes what they own in workspaces they are not in to the primary owner. A removed member's entry restores them as an organization member in no workspace, and takes only `name`. `remove: true` removes a member from the organization, or cancels the invitation pending to that address; removing a co-owner is the primary owner's. Each result says which changed: `added_to_workspace`, `workspace_role_changed`, `removed_from_workspace`, `organization_role_changed`, `removed`, `restored`. Sign-in names are compared in lowercase. A person adds a managed member and sets its password in Settings → Members. The primary owner is never removed, demoted or given a workspace role. In `groups`, an entry sets `name`, `description` and the roster with `member_ids`, or with `add_member_ids` and `remove_member_ids` that leave the rest in place; a roster entry may be a key of `members`, so a person invited in the same call can join; `null` deletes the group. The whole input is checked before anything is written or sent; members are applied before groups, in the order given. A workspace admin's tool list carries `set_workspace` and not `set_members`; a member's carries neither.
|
|
27
27
|
|
|
28
|
-
`set_access` gives members
|
|
28
|
+
`set_access` gives members or groups in the workspace, or everyone in it (`organization`), a role on resources. A share with someone outside the workspace, or with a group holding anyone outside it, is refused as outside the workspace; an organization owner adds them first with `set_members` (`role: "member"`), then the share is made again. Role `owner`, on one member, hands every resource listed to that member, who is in the resource's workspace and whom only the resource's owner or an admin may name; a call cannot share an app and hand it over together, an app handed to or from a member loses its sharing, and an automation is turned off until its new owner turns it on. Handovers are applied one resource at a time, and a failure part-way names what was already applied. `set_workspace` takes `credit_limits` (`workspace`, `apps` by app id, `members` by member id; a number is the daily ceiling in credits, `null` removes it and asks for approval).
|
|
29
29
|
|
|
30
30
|
## Comments
|
|
31
31
|
|