Platform

Permissions and Access Control

Lotics has a complete identity and access management (IAM) system that controls who can see and do what across the entire workspace. Every table, view, app, document template, automation, and workflow is protected by the same authorization model. This works for both human team members and AI agents — an API key and the AI assistant are bound by the same authorization model as everyone else.

Why this matters

In operational environments — where gate clerks, operations managers, accountants, sales reps, and external customers all touch the same data — access control is the difference between a toy and a system of record. A gate clerk should see container status but not billing rates. A customer portal should show only that customer’s shipments. An automation should be able to update records on behalf of the team without giving the triggering user direct write access.

Lotics handles all of this through a single, additive authorization model with no configuration code required.

Roles

Your organization holds its workspaces — one per business, branch or team that works on its own. Everyone has a role in the organization, and a role in each workspace they are in.

Role Where What they can do
Primary owner The organization Everything a co-owner can. Makes and removes co-owners, and resets a co-owner’s password. The organization’s creator, until they hand the organization to a co-owner in Settings → Members and become a co-owner themselves; cannot be removed.
Co-owner The organization Admin of every workspace. Manages everyone in the organization (invite, remove, restore, roles), every workspace’s groups, API keys and access log, billing, usage, workspaces and the organization’s settings, and can preview what a member sees.
Workspace admin One workspace Everything inside that workspace: its people and their roles there, its groups, API keys and access log, its settings and standing instructions, sharing, apps and publishing them, tables, templates, documents, workflows, connections and backups. Opens every item in it.
Member One workspace Creates items there, manages what they own, and uses what is shared with them.

Someone works in a workspace only once an admin of it, a co-owner or the primary owner adds them to it, as its admin or as a member. What they own and what is shared with them counts only in a workspace they are in.

An admin can open anything in their workspace, and their lists stay short. By default an admin sees what they made and what is shared with them, like everyone else, so a colleague’s private work doesn’t crowd their screens or their AI assistant’s answers. When they need the rest, Show all in the menu on Apps and Tables, and View in the Library, lists everything in the workspace, and they can open any of it. Each list remembers that choice on their browser until they turn it off. Automations and connections always list in full for admins. A private document is private from other members, not from the workspace’s admins, so who may read something sensitive is decided by who you make an admin of that workspace. An admin who keeps coming back to an item can share it with themselves, and it joins their list.

Adding someone to a workspace

An admin of the workspace, a co-owner or the primary owner does it, in Settings → Members or by asking the AI assistant:

  • Invite an email address to the workspace, as its admin or a member. The person joins the organization as a member when they accept. An address already invited to another workspace gets a place in this one on the same invitation.
  • Add someone who already works in another workspace of the organization, or change their role here. Someone who works in no workspace yet is added by a co-owner or the primary owner.
  • Create a worker who has no email, in the workspace, with a sign-in name and a password you give them. This one is done in Settings → Members only.

Admins of a workspace are equals: one can change another’s role or take them out of it. A workspace admin never changes a co-owner or the primary owner.

Renaming someone, resetting their password and removing them from the organization reach everywhere that person works. A workspace admin does these only for their own people: someone who works in no workspace the admin does not run, and who is not a co-owner or the primary owner. For anyone else, a co-owner or the primary owner does it. Restoring a removed person, from the Removed list, and changing someone’s role in the organization stay with the co-owners and the primary owner. All of these are done in Settings → Members; the AI assistant changes only who is in a workspace, their role there and its groups.

Sharing works only with people in the workspace. Sharing a table, an app or a document with someone who is not in it, or with a group of another workspace, is refused and says so: add them to the workspace first.

Resource roles

Each resource type has specific roles that control what a member can do with it.

Resource Available roles What each role allows
Table Viewer, Editor, Manager Viewer: see data, press buttons. Editor: see and edit data. Manager: edit data, change the table’s fields and settings, unlock its records, approve requests to change locked ones, and choose whether such changes wait for approval or are saved right away.
App User, Manager User: use the app (view data, submit forms, trigger actions), and read back their own agent runs in it. Manager: use it, and read every member’s agent runs in it. Its name, icon, sharing and everything about how it is built stay with the app’s owner and admins — see Who can build apps.
Skill User, Manager User: invoke the skill in chat. Manager: edit skill instructions.
Document template User, Manager User: generate documents from the template. Manager: edit template.

The person who created a table manages it, as does anyone it is shared with as Manager. The workspace’s admins can manage any table in it. Sharing a table stays with its creator and the workspace’s admins.

Sharing

Resources can be shared with three types of targets:

  • Individual member — grants access to one person.
  • Group — grants access to all members of the group. Adding a member to the group immediately grants them access. Removing them immediately revokes it.
  • Everyone in the workspace — grants access to every person in the workspace. People added to the workspace automatically get access. People who leave it automatically lose it.

The workspace’s admins and resource owners can share resources. If a member receives access from multiple sources (direct share + group + everyone in the workspace), they get the highest role. The model is purely additive — there is no “deny” rule.

Groups

Groups are named sets of members used as sharing targets. They simplify access management when you have teams or departments that should see the same resources.

  • A group belongs to one workspace, and only people of that workspace can be in it. The workspace’s admins create and manage its groups, in Settings → Members.
  • A group is shared with only inside its own workspace.
  • Taking someone out of a workspace takes them out of its groups too.
  • A member can belong to multiple groups.
  • Groups have no management powers — they exist purely for sharing.
  • Deleting a group removes all access granted through it.

Example: create a “Finance” group, add the accountant and finance manager. Share the Invoices table with “Finance” as Editor. Both members can edit invoices. When a new finance hire joins, add them to the group — they immediately get access.

Standing in while you are away

In an app where each step of the work has an owner — a request waiting on the director, a payment on the accountant — the step should not stall while its owner is on leave. Set it yourself in Settings → Away: the first and last day you are away and the colleague who stands in for you.

  • On those days, every step that is yours — by name, or through a group you are in — also waits on the one standing in. The step says so: “Lê Văn Sơn · thay Trần Thị Mai đến 08/10” (standing in for Trần Thị Mai until 08/10).
  • It stays yours too: you can still act on it.
  • The one standing in reaches it only through apps they can already use, and never approves a request they made themselves or a second level of the same request.
  • Only a colleague who works in your organization now can stand in.
  • An absence runs at most 60 days, the first and last both counted; to stay away longer, set it again. Press End absence to end it early.
  • A co-owner or the primary owner can end anyone’s absence: in Settings → Members, where each member away is marked on their row, open the member and press End absence.
  • Each absence set or ended is written to Settings → Access log, naming who did it.

Access log

Settings → Access log lists who changed access, and when. An admin of a workspace reads that workspace’s log: changes to its tables, apps and other items, who they were shared with, who was added to the workspace, given a new role there or taken out, accounts created in it, handovers of ownership, and its groups. Changes that reach beyond one workspace — a password reset, a rename, a removal from the organization, an invitation — and keys that reach several workspaces are in the log of the co-owners and the primary owner, who read every workspace’s.

Ownership

Every resource has an owner — the member who created it. Ownership determines:

  1. Who manages the resource — the owner can edit structure, configure sharing, and delete the resource.
  2. Runtime authority — when automations, workflows, and apps execute, they run with the owner’s current permissions (see below).
  3. Lifecycle — when a member leaves a workspace or the organization, their resources pass to someone who stays, and their automations are turned off (see When someone leaves).

The workspace’s admins can transfer ownership to anyone in the workspace.

Runtime authority for automations and apps

Automations, workflows, and apps run with the owner’s permissions, not the triggering user’s permissions.

What this means in practice:

  • A gate clerk with Viewer access presses a button on a container record. The button triggers a workflow that updates the container status, generates a gate-in receipt PDF, and sends an email. The workflow succeeds because it runs with the owner’s (admin’s) permissions, even though the clerk only has Viewer access.
  • An app built by an admin shows billing data from multiple tables. A sales rep with User access on the app sees the data through the app, even without direct access to the billing tables.
  • An automation triggers when an email arrives. It queries a related table, cross-checks values, and updates a third table. All of this works because the automation runs with the owner’s permissions, not the triggering event’s context.

The rule: if the owner is an admin of the workspace, the workflow/automation/app has full access to that workspace. If the owner is a regular member, it can only access resources the owner can access. If the owner loses access, the workflow fails; if the owner is no longer in the workspace, it does not run, and the workspace’s admins are told.

Who can build apps

Who
Create an app Any member, in a workspace they can reach. Whoever creates it owns it.
Build it — write its screens, set its queries, workflows and agents, deploy a new version Its owner, or an admin of the workspace
Share it with a member, a group or everyone in the workspace Its owner, or an admin of the workspace
Share it with anyone who has the link An admin of the workspace

Building an app is the owner’s because an app runs with its owner’s permissions: what you build reaches exactly what you reach, and no more. That is also why a Manager share does not let you build somebody else’s app — you would be writing something that runs with their access, not yours. Share the app with them as Manager if they should run it; transfer it to them if they should build it.

Sharing an app with anyone who has the link is a workspace admin’s decision, because the people it reaches are not people the organization can ask.

Transferring an app to or from a member clears who it is shared with, including a public link. The app’s reach follows its owner, so the new owner decides who sees it rather than inheriting an audience. Between two admins of the workspace, whose reach there is the same, the app keeps its shares.

API keys, terminals and AI agents

A key created in Settings → API keys has its own access, chosen on the key: All apps and tables in the workspaces you choose, or Only selected ones — and for the second, which apps and tables, each at its own level. An admin of a workspace creates and manages the keys of that workspace; a co-owner or the primary owner manages every key, across workspaces. A key set to All apps and tables does not reach a workspace created after it until that workspace is added to the key. That list is changed on the key’s own screen at any time; a resource’s Share dialog shows a key that reaches it and lets that access be taken away, but adds none. Its Can setting narrows the key further, never widens it. What a key creates belongs to the key, and an admin of its workspace can transfer any of it to a person. A key created for a person carries that person’s access instead — the key list shows Acts as and their name for one — and it stops working when that person is removed.

A command-line sign-in (lotics auth login) acts as you. You can see and end it yourself at Settings -> Security, and lotics auth logout ends it too — either way it stops working for good and leaves the list. A key belongs to the organization, so logging out only removes it from your machine.

An AI assistant you connect over MCP — ChatGPT, Claude — also acts as you, in the workspaces you ticked when you approved it, with your role in each. You can see and disconnect it at Settings -> Security, and a co-owner or the primary owner can see and disconnect members’ at Settings -> API keys. Disconnecting ends its access at once; removing it inside the assistant does not.

The AI assistant in the chat acts as the chatting member. It can only access what that member can access. This means:

  • An admin of the workspace chatting with the AI assistant can ask it to do anything across the workspace. It answers from the documents the admin lists unless asked to look at all of them.
  • A member chatting with the AI assistant can only interact with resources shared with them.
  • A key set to All apps and tables reaches every app and table of the workspaces chosen on it. A key set to Only selected ones reaches the apps and tables named on it, and nothing else.

Who sees which rows in an app

An app decides who sees which of its rows. Without a rule, everyone the app is shared with sees every row it shows. Where people should see different rows — “each sales rep sees only their own customers”, “each branch manager sees their branch” — the app states that rule for the table, and it holds everywhere the app reaches: its screens, what an AI assistant reads and writes through it, its buttons and its automated steps. Ask the AI assistant building the app to state it, in your own words.

  • The rule holds for the workspace’s admins too. People who should see every row in the app, such as managers, are named in it as a group.
  • Someone opening the app by a public link, without signing in, sees no row a “their own” rule would choose.
  • The rule never reaches past the app’s owner: an app shows only rows its owner can read.
You want What the app needs
Everyone on the team sees every order Nothing — share the app
Each sales rep sees only their own deals A rule: each rep sees the deals they are assigned to
Reps see their own deals, managers see all A rule: a rep sees their own deals, and the Managers group sees every deal
Each branch manager sees their branch’s orders A rule: a manager sees the orders of the branch they manage
Employees see their own payslips, HR sees all Two apps: one with the rule “each employee sees their own payslips”, one for HR without it
Team leads see their people, not salaries An app that does not show the salary — what an app does not show, no one reads through it

An app that opens on one branch or one project at a time is not a rule by itself: anyone it is shared with can switch to another branch. State the rule too.

Data visibility rules on tables

A table’s own row-level visibility rule restricts which records members see when they open the table itself — its views, search, exports and the API. For example: “sales reps see only their own deals.” Inside an app, the app’s rule decides instead (above); the table’s rule still limits what the app’s owner can show.

Who bypasses visibility rules:

  • The workspace’s admins
  • The table owner
  • Workflows and automations owned by an admin of the workspace
  • API keys set to All apps and tables, in the workspaces chosen on them

Who follows visibility rules:

  • All other members, regardless of their table role
  • API keys set to Only selected ones, and command-line sign-ins (which follow the rules of the person they act as)
  • Workflows owned by non-admin members

A key set to Only selected ones follows the rule as itself, and a rule written against whoever is asking — “sales reps see only their own deals”, which reads a field holding people — matches no key, so a table given to one that way answers it with no rows at all. Give the key a table whose rule does not depend on who is asking, or set it to All apps and tables.

Visibility rules on a table are enforced on every direct path: table access, views, search, filters, exports and the API.

Connections

A connection to a mailbox, an accounting system, a page or any other service belongs to the organization, not to the person who set it up.

  • Only an admin of the workspace connects an account, in Settings -> Connections. Connecting a mailbox or a Drive makes it the organization’s, so a private inbox belongs in your own assistant, not here.
  • The workspace’s admins, and anyone it is shared with, can act through it. Nobody ever sees the credential.
  • When its owner leaves, it passes on with the rest of their work and keeps working. If a person’s data is erased, a mailbox or Drive whose login is their own address is deleted; any other connection they made stays with the organization.
  • A write through a connection from chat asks first and is recorded in the access log.
  • An automation that reads a mailbox stops and tells its owner when they can no longer use the connection.
  • A workflow must name its connection in the workflow itself, so what it can use is checked when it is saved. A connection read from a record or an input is refused.

Notification cards

An action on a notification card runs a notification workflow, a workflow with one owner for life. Pressing the action only starts it: it runs with its owner’s permissions, and its owner or an admin changes it or puts it on a card. When its owner leaves the organization or the workspace it is archived and its open cards close. A notification reaches only people in its workspace.

Linked records and cross-table access

Tables can link to records in other tables. When a record links to a record in another table, the linked record’s display text is visible to anyone who can see the link field.

  • No access to linked table — you see the display text only, cannot expand or navigate to the linked record.
  • Access to linked table — you can see the linked record based on your own permissions.

Sharing a table grants that table and nothing else — a linked table needs its own share.

A filter that looks through a link, and a link’s record picker, read the linked table, so they work only for people who can open it. A saved view that filters this way shows someone who cannot open that table a message on that view, and their other views work. Where a visibility rule narrows the linked table for them, the filter matches only through rows they can see. A stored title or lookup on the row stays readable, because the table’s author chose to keep it there. Hiding a column in a view is layout, not access: to keep a column from someone, give them an app that does not show it.

Writing a new link needs you to be able to read the row you link to, and so does asking for one in a change request. When some people who can open a table cannot open a table its links reach, Lotics says so: after you save the link, and in both tables’ share dialogs. The notice names them and, if you own the linked table or are an admin of the workspace, offers to share it with them as viewer.

Lifecycle events

When someone leaves a workspace

When an admin of the workspace, a co-owner or the primary owner takes someone out of it:

  1. Everything shared with them in that workspace stops reaching them, and they leave its groups.
  2. What they own there passes to the person who took them out. Automations pass turned off, for the new owner to turn on; notification workflows are archived and their open cards close.
  3. Their work in other workspaces, and their place in the organization, stay as they were.

When someone leaves the organization (offboarding)

When a member is removed from the organization — by a co-owner or the primary owner, or by an admin of the only workspaces the person works in:

  1. Automations they own are disabled.
  2. Ownership of their resources is transferred to a co-owner or the primary owner. That includes the table checks they saved, which from then on read records with that person’s access, so they get a notification in each workspace naming the checks that came to them.
  3. They leave every workspace. All role bindings and group memberships are removed, and so are their absence and every absence naming them to stand in. The access log records each of those other absences as ended by whoever removed them.
  4. Every credential acting as them is revoked — their command-line sign-ins, any key that acts as them, and the AI assistants they connected over MCP.

Only the primary owner removes a co-owner. No resources are deleted — everything is preserved under new ownership. An app that passes from a member this way also loses who it was shared with, so the new owner decides that afresh; one that passes between two admins keeps it, so its staff don’t lose it. If you restore the member later, they come back as a member of the organization in no workspace, with their credentials still revoked: add them to the workspaces they need, and they sign in and connect their assistants again.

Role changes

  • A co-owner made a member (the primary owner’s decision) keeps the workspaces they were added to. In every other workspace, what they own passes to the primary owner.
  • A workspace admin made a member keeps what they own. Their automations and apps that relied on admin access to the whole workspace fail at execution time, and they can only access what is shared with them.

Resource deletion

  • Table deleted — refused while an app or a workflow elsewhere still references the table. Once nothing does, the table’s views are deleted with it.
  • App deleted — app action workflows deleted.
  • Group deleted — all access granted through it removed.

Frequently asked questions

Can I give a customer access to only their own data?

Yes. Create an app that filters data by customer, share it with the customer as User. The app runs with the owner’s permissions, so the customer sees only what the app exposes — they don’t get direct table access. Give the app the rule “each customer sees only their own records” and that holds on every screen, button and assistant request in it.

Can an automation access tables that the triggering user cannot?

Yes. Automations run with the owner’s permissions, not the triggering user’s. If the owner is an admin of the workspace, the automation has full access to it. This is the core mechanism that makes shared workflows useful — a Viewer can press a button that triggers writes to tables they cannot access directly.

What happens when someone leaves the team?

Their automations are disabled, their resources and connections are transferred to a co-owner or the primary owner, all their access is revoked, and every credential acting as them is revoked with them. An API key with its own access is not one of them — it is not that person — so the integrations running on it keep running. No data is deleted.

How do API keys work with permissions?

A key has its own access, set on the key: All apps and tables reaches everything in the workspaces chosen on it, Only selected ones reaches the apps and tables named on it and nothing else. A key’s Can setting narrows it further — a key that may only read data cannot write, whatever its Access reaches. Keys are created in Settings -> API keys, by an admin of the workspace or a co-owner, and use the format ltk_ followed by 48 characters.

Can I scope an AI agent’s access?

Yes, on two axes. Create the key with Only selected ones and give it just the apps and tables the agent needs — it reaches those and nothing else — and set the key’s Can to the operations it actually performs.

Can a member build an app?

Yes. Any member can create one, and whoever creates it builds it. What the app can reach is what that member can reach, so a member’s app cannot show data they could not open themselves. Sharing it with anyone who has the link stays a workspace admin’s decision.

Sign up for Lotics

We'll reach out within a day.