Products
A product is a workspace of its own in your organisation, in which your team builds. Every client workspace of the product gets a copy of what is set to In the product there. Create a product when several clients are to get the same agents and workflows. Products exist only for a partner.
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
Create a product
- In the organisation, open Products.
- Click Create product.
- Enter the name under Name.
- Click Create.
lowcloud creates the product workspace and switches to it. Every member of the organisation gets a seat there with their role. Anyone who joins the organisation later needs an invitation to the product workspace.
The name of the product is also the name of the workspace. It is shown in the browser tab and in the name of the base chat. This also applies in every client workspace of the product, as long as no name of its own is set there. You change it in the Settings of the product workspace under Name of the product.
The product workspace gets its credit for building and testing from the organisation. To transfer it, click Transfer credit in the row menu of the product on the page Products.
The page Products lists every product with its domain, its number of clients and its credit. A click on the row opens the product workspace if you are a member there. The row menu also leads to Settings and Manage team. The products are also in the sidebar of the organisation under Products and in the workspace switcher in the group Products. A product workspace does not count as a client and takes up no client slot.
Build for the product
In the product workspace you build agents and workflows as in any other workspace. The visibility chip has two values there:
- Private: only you see the agent or workflow. No client gets it.
- In the product: everyone in the product workspace sees it, and your clients get it with the next rollout.
A workflow set to In the product is rolled out only once it has a published version. Until then it carries the badge Not published in the Dashboard. The base chat is never rolled out.
Assign client workspaces
Open the Dashboard in the product workspace. In the section Client workspaces you take clients in in two ways:
- Create client workspace: creates a new client workspace in the product. You enter the Name of the client and the Starting credit and click Create. You invite the client's people afterwards in the settings of the client workspace.
- Assign: takes in an existing client workspace of your organisation. Choose it from the list and confirm with Assign.
In both cases lowcloud rolls out at once.
A client workspace belongs to one product at most. If you assign one that is already in another product, the agents and workflows of that product stay in the workspace. They no longer get updates.
From a client workspace of the product, the way back at the top of the sidebar leads to the product if you are a member there, otherwise to the organisation.
Roll out
Changes in the product never reach the clients by themselves. You roll them out.
- Open the Dashboard in the product workspace.
- Click Roll out in the row of the client. If changes are waiting for more than one client, Roll out to all is shown at the top.
- In the dialog, check what is added for each client, what is updated and which adapted copies stay unchanged.
- Click Roll out.
A rollout writes only what is new for the client or has an update. Current copies stay untouched. A copy keeps its chats, its prices, its access and its setups.
What an agent or workflow needs comes along: documents, skills, subagents and the agents a workflow uses in its steps. Buckets arrive empty.
State per client
The section Client workspaces shows for each client when the last rollout was, the number of members and the credit. If something new or an update is waiting, the row carries the badge New changes.
The section Agents and workflows lists everything that is set to In the product. A click on a row shows the state of the copy per client:
| State | Meaning |
|---|---|
| New | The client has no copy yet. |
| Update available | The product has changed since the last rollout. |
| Current | The copy matches the state in the product. |
| Adapted | The copy was adapted for this client and gets no updates. |
Setups of the clients
When a workflow is rolled out in a new version, lowcloud moves the setups of the client's people to that version. If the new version does something new on a person's accounts, for instance through a different trigger or an additional action, that person's setup stays on the old version. The person then updates it themselves, see Publishing and setup. After the rollout, the dialog says how many setups this concerns.
What cannot be rolled out
In the section Agents and workflows, such an entry carries the badge Cannot be rolled out. The reason is in the tooltip. Everything else is rolled out anyway.
- an agent or workflow step that uses a custom integration or an MCP server
- a workflow with a webhook trigger
- an agent with a subagent that is not set to In the product
- a workflow with a step that uses an agent that is not set to In the product
- everything that uses one of these agents
Adapt a copy for a client
In the client workspace, a notice with the name of the product is shown above every copy. As long as the copy is connected, only the product changes its instruction, its tools and its settings. The copy's own knowledge, its access, its prices, its chats and its setups belong to the client workspace.
- Open the copy in the client workspace.
- Click Adapt for this client in the notice.
- Confirm with Adapt.
After that you change the copy freely. Updates from the product no longer arrive.
With Reconnect in the same notice you bring back the state of the product. You get the same at a rollout with Also overwrite adapted copies, for all adapted copies of the chosen clients. To the product switches to the product workspace.
Remove a client workspace from the product
- Open the Dashboard in the product workspace.
- Click Remove in the row of the client.
- Confirm with Remove.
The agents and workflows stay in the client workspace, but no longer get updates. The workspace stays a client workspace of your organisation. If you assign it again later, unchanged copies get updates again.
Delete a product
A product can be deleted only as long as it has no clients. Remove all client workspaces from the product first.
- In the organisation, open Products.
- Click Delete in the row menu of the product.
- Type the name under Name of the product.
- Click Delete.
The product is deleted with its workspace and all agents, workflows and conversations in it. Its credit goes back to the organisation. Copies that former clients still have stay with them.
Set the client view
In the Settings of the product workspace, the section Client view sets what the people of all clients of the product see. Which switches there are is described under Partner.
The view applies in every client workspace of the product, as long as nothing of its own is set there. If you change a switch in a client workspace, only its own view applies there from then on. The section then carries the badge Adapted. Reset restores the view of the product.
Appearance and domain
An admin sets the logo and colour of the product in the Settings of the product workspace, in the section Appearance. Both also apply in every client workspace of the product, as long as nothing of its own is set there. If the product has set nothing either, the appearance of the organisation applies.
A product can get a domain of its own. lowcloud enters it. Under this address the client's people reach the client workspaces of the product, and invitations lead there. The product workspace itself stays reachable only under lowcloud's address. How signing in under an own domain works is described under Partner.
Limits
| Limit | Value |
|---|---|
| Name of the product | 40 characters |
| Products per client workspace | 1 |
The page Products and the Dashboard do not open on a phone.
Permissions
| Task | Who may |
|---|---|
| Create a product, transfer credit to a product | anyone who may build in the organisation (the role admin, or the former role developer) |
| Delete a product | admins of the organisation |
| Assign and remove clients, roll out | admins of the product workspace who may build in the organisation |
| Set the Client view | anyone who may build in the organisation |
| Build in the product and change the visibility | anyone who may build in the product workspace |
| Adapt and reconnect a copy | anyone from the partner's team who may build in the client workspace |