Workspace and roles
A workspace is the area that everything in lowcloud belongs to: workflows, agents, skills, knowledge, connections, runs and the credit. Only its members see what is in it, and nothing of it reaches into another workspace. Every member has a role: an admin builds and manages, a member uses what others have built.
Invite colleagues
- Open Settings > Members.
- Enter the email address.
- Choose the role member or admin. The role member is preselected.
- Click Invite.
The invited person gets an email with the button View invitation. On the invitation page they click Join or Reject. If they are not signed in yet, they sign in first and then come back to the invitation. After joining, the new workspace becomes active and the app reloads.
If the person is signed in with a different address, the page shows "Wrong account". The only way on is Sign out.
A new invitation to the same address replaces the one still open. Someone who is already a member cannot be invited.
Manage members
You manage members under Settings > Members. Only admins see this section.
Change a role
In the member's row, choose admin or member. A workspace can have several admins.
Set a monthly limit
In the member list you set a Monthly limit per member. What it caps and what happens when it is reached is described under Credit and costs.
Remove a member
Click the symbol at the end of the row and confirm with Yes, remove.
You can neither change nor remove your own row. You can change and remove other admins, but not the last one: a workspace needs at least one admin.
Withdraw an invitation
Open invitations appear as dashed rows in the member list. Click Withdraw in the row. The list hides expired invitations.
Switch workspace
You get into a further workspace only by invitation. You cannot create one yourself. The exception is a partner, who creates a client workspace for each client and a product workspace for each product, see Partner.
If you are a member of more than one workspace:
- At the bottom of the sidebar, click the name of the workspace next to your profile picture.
- In the group Workspace, choose the workspace. The active one carries a tick.
The app then reloads. If you are in only one workspace, the group is missing.
After signing out, lowcloud does not remember the workspace you used last. The next sign-in lands in your oldest membership, usually the personal workspace.
Rename the workspace
You get your first workspace automatically on the first page view after signing in. It carries your first name, for instance Anna's Workspace. Without a stored name it is called My workspace.
This is how an admin renames the workspace:
- Open Settings.
- In the section Name, enter the new name.
- Press Enter or leave the field.
Set the appearance
An admin sets name, logo and colour in the Settings, section Appearance. All three apply to all members of the workspace.
| Setting | Effect | Limit |
|---|---|---|
| Name | Replaces lowcloud in the browser tab and in the name of the base chat. The name of the workspace stays untouched. | 40 characters |
| Logo | Replaces the lowcloud logo in the sidebar. | PNG, JPEG or WebP up to 256 KB |
| Colour | Appears on buttons, highlights and active entries. |
On a light background, lowcloud shows a light colour darker so that text on it stays readable. With Restore default you reset the colour.
Sign in
On the sign-in page, click Sign in with Google or sign in with a magic link. A magic link is a one-time link that lowcloud sends you by email.
- Enter your email address and click Send magic link.
- Open the link in the email. It is valid for 15 minutes.
- Click Confirm sign-in.
The click in step 3 prevents security scanners from using up the one-time link beforehand. Until you open the link, the sign-in page offers Send link again and Use another email address.
Try it without an account
If you come from the website into the builder with a prompt, lowcloud signs you in anonymously. You get a workspace with 0.50 € of credit. Only one workflow is possible in it, and you see only the builder. Every other page redirects to the sign-in.
When the credit is used up, you sign in and keep building. With an account you get starting credit. Your work so far moves into your new workspace.
Delete your account
- Open My account via the user menu.
- In the section Delete account, click Delete account. The dialog shows for each of your workspaces what happens to it.
- Type your email address to confirm.
- Click Delete account permanently.
| Your situation in the workspace | What happens |
|---|---|
| You are the only member | The workspace is deleted, with all agents, workflows, files and runs. |
| There are further members | You leave. Your private content is deleted. What the team sees stays. |
| You are the only admin beside further members | Deleting is blocked until you make someone else an admin. |
| You are the only member of an organisation with clients | Deleting is blocked. Get in touch with lowcloud first. |
With the account, your connections, chats, files and settings are deleted. Usage figures stay in the billing without your name.
Limits
| Limit | Value |
|---|---|
| Members per workspace | 25 |
When the workspace is full, lowcloud rejects every further invitation with "The team has reached the maximum size."
Kinds of workspace
Most accounts work in a single workspace. A partner has an organisation with several workspaces below it.
Workspace
Admins build and manage. Members use what has been built.
Organisation of a partner
Holds the team, the credit and the clients. No chat, no building.
Internal workspace
The team builds for itself.
Product workspace
The team builds what several clients get.
Roll out: copies for the client workspaces of the product
Client workspace
One per client, with its own members and its own credit.
- Team of the partner
- builds as admin
- People of the client
- admin or member, never build
| Kind | How it comes into being | Who builds there |
|---|---|---|
| Workspace | lowcloud creates it on the first page view after signing in. | anyone who may build |
| Organisation | lowcloud creates it above an existing workspace. | nobody, it has no pages for building |
| Internal workspace | It is the workspace above which the organisation was created. | the partner's team |
| Product workspace | The partner creates a product. | the partner's team |
| Client workspace | The partner creates it for a client. | the partner's team, never the client's people |
Roles
Only the roles admin and member are assigned, at invitation and at a role change. A role applies per workspace: the same person can be an admin in one workspace and a member in another.
| Admin | Member | |
|---|---|---|
| Build and publish workflows, agents, skills | yes | no |
| Write knowledge and documents, create integrations and MCP servers | yes | no |
| Set the default model of the workspace | yes | no |
| Open the Dashboard | yes | no |
| Start published workflows and set them up for themselves | yes | yes |
| Chat with agents, answer approvals | yes | yes |
| Create their own connections | yes | yes |
| See the credit amount of the workspace | yes | no |
| Invite members, change their role, remove them | yes | no |
| Set a Monthly limit per member | yes | no |
| Restrict the Access to an agent or workflow to individual members | yes | no |
| Rename the workspace, set the Appearance | yes | no |
A member runs the workflows they set up for themselves through their own accounts. They resume their own interrupted runs. They change nothing that was built. In the sidebar, Skills, Knowledge, Buckets, Dashboard and Clients are missing for them.
In a partner's organisation, the role also decides who sees the clients, see Partner.
In a partner's client workspace
In a client workspace, only the partner's team builds. For the client's people this applies:
| Admin of the client | Member of the client | |
|---|---|---|
| Chat, use agents and workflows, answer approvals | yes | yes |
| Connect services | yes, as far as the partner allows them | yes, as far as the partner allows them |
| Build agents, workflows and skills | no | no |
| Invite members, change their role, remove them | yes | no |
| Set a Monthly limit per member | yes | no |
| Restrict the Access to an agent or workflow | yes | no |
| Open the Dashboard | yes, as long as the partner has not hidden it | no |
| See the credit amount | yes | no |
What the partner can hide from the client's people is described under Partner.
Former role developer
The role developer is no longer assigned. It only remains on old memberships. A developer builds, sets the default model of the workspace and sees the credit amount. They cannot manage members or open the Dashboard.
In the member list, developer cannot be selected. The role stays until an admin changes it to admin or member.