Partner

Create a client workspace for each client, build in it and offer prices.

In lowcloud a partner is an organisation above several workspaces: one internal workspace for its own team and one client workspace per client. You create the client workspace yourself and build in it as admin. You invite the client's people afterwards.

If several clients are to get the same agents and workflows, you create a product. How the workspaces relate is shown in the overview under Workspace and roles.

Create a client workspace

  1. In the organisation, open Clients.
  2. Click Create client workspace.
  3. Enter the name under Name of the client, for instance Miller Ltd. All members of the workspace see it in the sidebar.
  4. Enter an amount under Starting credit. It comes out of the organisation's credit.
  5. Click Create and switch there.

lowcloud creates the workspace and switches to it. You are admin there. A starting credit of 0 € is possible, but without credit nothing runs in the new workspace. If all client slots are occupied, you cannot create another client workspace.

In a client workspace, the sidebar shows your team the name of the organisation at the top. A click on it leads back to the organisation. If the client workspace belongs to a product in which you are a member, the product is shown there, and the click leads to it. The workspace switcher sorts your workspaces into the groups Organisation, Internal workspace, Products, Clients and Workspaces.

You build directly in the client workspace. You bring an agent or workflow from another workspace, for instance the internal workspace, there with Share as link. How this works is described for agents under Sharing and access and for workflows under Publishing and setup.

Invite the client

The client's people come into the client workspace by invitation, as admin or as member. As an admin of the client workspace, you invite them in one of two places:

  • in the Settings of the client workspace, section Members
  • on the client page, tab Members

How an invitation works is described under Workspace and roles.

In the tab Members of the client page you also change roles, remove members and set a monthly limit per member in the column Limit. If you are not an admin of the client workspace, you can only read the list.

If the client is to manage their workspace themselves, invite them as admin.

Set the client view

In the Settings of a client workspace, the section Client view sets what the client's people see. The switches apply to the client's admins and members. Your team still sees everything.

GroupWhat you switch on and off
Sidebarthe entries Agents, Approvals, Runs, Files and Dashboard
Dashboardthe tabs Usage, Agents, History and Members
Connectionswhich services the client's people may connect

For all clients of a product you set the view once in the product workspace, see Products.

Hidden pages stay reachable via links, for instance from notifications. If the tab Usage is hidden, the client sees no usage amounts anywhere, only the credit. The client never sees functions for building, whatever the switches say.

Transfer credit

Credit for the internal workspace, the product workspaces and the client workspaces comes out of the organisation's credit.

  1. Click Transfer credit. The entry is in the row menu of every client and every product and on the client page. For the internal workspace, the button is in the Settings of the organisation, section Credit.
  2. Under Amount, enter between 1 € and 500 €.
  3. Click Transfer.

The credit is used in the workspace that receives it. You cannot transfer more than the organisation's credit.

The organisation's credit is shown in its settings. It is topped up via lowcloud, as in any workspace, see Credit and costs.

Offer prices

In the tab Prices you offer the client a price per agent or workflow. The tab is on the client page and in the Dashboard of the client workspace. Only what the whole team sees can get a price. You can make an offer only as a member of the client workspace.

  1. Click Offer price in the row.
  2. Enter the Base fee, per month and net. It is also due in months without use.
  3. Choose the Usage rule.
  4. If you like, add a Sentence to the client.
  5. Click Make offer.

The usage rule has two options:

  • By usage: the client pays the usage on top of the base fee.
  • Included: the usage is part of the base fee, and you bear it.

An admin of the client accepts or rejects the offer in the Dashboard, tab Prices. You cannot accept your own offer. If the client workspace has no admin outside your team yet, you cannot make an offer.

As long as the first offer is open, the agent or workflow is locked for the client. The lock stays after a rejection too.

The lock ends when the client accepts a new offer or you click Drop price.

The price starts on the day of acceptance and is charged pro rata for that month. You write the invoice to the client yourself. Below the list is your split: Base fees per month, Share of lowcloud and Stays with you.

Organisation

An organisation sits above a partner's workspaces. The team, the credit and the clients belong to it. The organisation itself has no chat and no pages for building. Its sidebar shows the internal workspace, Clients, Products and Settings. Under Clients and Products are the individual client workspaces and products.

An organisation has exactly one internal workspace. Your team builds there for itself. It does not count as a client and takes up no client slot. In addition there is one workspace per product. It takes up no client slot either.

lowcloud creates an organisation above an existing workspace. That workspace becomes its internal workspace. Its members come into the organisation with their role, and its credit moves to the organisation. You cannot make yourself a partner.

SettingWho sets itMeaning
Namean admin, in the Settings under Name of the organisationClients see the partner under this name in their settings.
Client slotslowcloudHow many client workspaces the organisation may have: 1 to 500, preset to 10
Own domainlowcloudThe address under which clients reach their client workspaces

In the section Appearance of the settings an admin sets name, logo and colour. In an organisation they also apply in every client workspace as long as nothing of its own is set there. If a client workspace belongs to a product, the name, logo and colour of the product apply first.

lowcloud can lock an organisation instead of deleting it. It then keeps its clients. But the page Clients no longer opens, and new client workspaces cannot be created.

Clients page

At the top of the page Clients are the occupancy of the client slots, for instance 3 of 10 slots occupied, and the button Create client workspace. If there are products, you filter the list by product. You open the internal workspace via the sidebar, the products via the page Products.

The table shows for each client workspace the name, its product, since when it has belonged to the organisation, the number of members, workflows and runs, the last run, and the usage and remaining credit in euros.

What a click on a row opens depends on whether you are a member of that client workspace:

  • With a membership: you switch into the client workspace.
  • Without a membership: the row carries the badge Figures only. The click opens the client page.

At first only the person who created the client workspace is a member. Colleagues from your team see Figures only until they are members there. The menu at the end of the row offers View figures and Transfer credit, and with a membership also Open and Manage members.

The client page has the tabs Overview, Usage, Prices, Agents, History and Members. If you are a member of the client workspace, Work in the workspace and Open in the workspace lead straight there.

The page Clients does not open on a phone.

Differences from an ordinary workspace

A client workspace has its own members, its own content and its own credit. It uses its own credit, not that of the organisation.

Client workspaceOrdinary workspace
First adminthe person from the partner's team who creates itthe person for whom lowcloud creates it
Starting creditnone from lowcloud, the partner sets it when creatinga starting credit from lowcloud
Buildinganyone from the partner's team who may buildanyone who may build
Section Default modelonly for those from the partner's team who may buildfor anyone who may build
Topping upvia the partnerget in touch with lowcloud

The client's people see no functions for building, not even as admin. They chat, use agents and workflows, answer approvals and connect services. An admin of the client also manages members and monthly limits and opens the Dashboard, as long as you have not hidden it.

Own domain

An organisation can get a domain of its own, and so can each of its products. lowcloud enters it.

Under the domain of the organisation the client's people reach all client workspaces of the organisation, under the domain of a product only the client workspaces of that product. Invitations into a client workspace lead to the domain of its product, otherwise to the domain of the organisation. Signing in there works only by magic link. Anyone who is not a member of a client workspace under the address reads "Your account belongs to no workspace under this address." after signing in.

The sign-in page shows the appearance of the product or the organisation. If no logo is set, the name is shown there.

The organisation, its internal workspace and its product workspaces stay reachable only under lowcloud's address.

Permissions

In an active organisation, the entries Clients and Products are visible only to anyone who may build (the role admin, or the former role developer). Anyone with the role member in the organisation does not see them and does not reach the pages via the address either. This way the role in the organisation decides who sees the figures of all clients.

Members of the organisation who may build see the section Client view.

Without a membership in the client workspace you see only the figures of the client page. You do not see content such as messages, documents or results of runs. Anyone from your team who is a member of the client workspace sees the content like any other member.

In their Settings, section Partner, the client sees which organisation looks after them and what it sees: usage, credit and activity, the names of the agents and workflows, the email addresses and roles of the members and a history with one entry per chat message and per run.

Neither you nor the client can end the relationship in the interface.