Workspace scope
Company workspaces are separated and access is tied to approved identities.
Workspace separation, hashed access keys, scoped roles and approval trails shape how Luama AI operates.
Company workspaces are separated and access is tied to approved identities.
Issued access keys are stored hashed and are not displayed again.
Sensitive actions can require human approval and produce operational records.
Request a workspace for your company, or sign in if Bordales has already approved your account.
Luama AI maps the workflow, channels, approvals, data boundaries, reporting and support path before the build is activated.
Yes. High-risk messages and workflow actions can stop for human review before anything is sent or changed.
Yes. Approved customers receive a workspace with scoped users, channels, workflows and operational records.