← All guides

Organisation · 3 min read

Builder

Builder is where a workspace defines modules of its own and reads what it already enforces: its rules, its workflows and the records it holds.

Builder is being reworked, so for now it appears only in the workspaces that run Rople itself. If your sidebar has no Organisation › Builder row, that is why; nothing is wrong with your workspace. Everything below describes the screen as it stands, for the workspaces that have it.

The page has four tabs: Modules, Rules, Workflows and Records.

Group
Organisation
Where
rople.app/w/builder
Who can open it
not offered to customer workspaces yet; in the workspaces that run Rople itself, level 3 and above, and level 4 to change a module

Modules

A module here is a name in the sidebar, a place in it, a seat floor, and a dataset behind it. The dataset is a workflow, so a module built here gets the workflow's table, board and other views without any of it being built twice.

Define a module opens a sheet:

  • Name. What people will see in the sidebar. The name also makes the module's address, so renaming it later changes the link.
  • Description. One line on what it is for. Optional.
  • Module. Which of the seven it belongs to. A module goes where its work goes, and the sidebar never grows an eighth.
  • Who can open it. The lowest seat that may open it: Everybody, Team leads and above, Managers and above, Executives, or Nobody in the workspace (Rople staff only), which no seat in the workspace holds.
  • What its records look like. A workflow template, with its stages, fields and owner sections, all editable afterwards. Decide later saves the module without one.

Press Create module. A module lives at its own address, rople.app/w/m/ followed by its slug, and has three states:

  • Draft. Saved and listed here, and in nobody's sidebar. It opens at its own address for a seat at or above its floor.
  • Live. In the sidebar, inside the module it belongs to, for every seat at or above the floor. Put live needs a dataset; a module saved with Decide later cannot go live until it has one.
  • Retired. Retire keeps the definition and its records, and closes the address, so a link somebody saved stops opening.

Each module in the list shows its state, its place, its floor and its address, with Open, and for level 4 Edit and Put live or Retire.

Rules

What this workspace enforces, read from the code that applies it. Each rule names the file somebody can open to check. This tab is a report rather than an editor: it says what the workspace does, not what Rople could do.

Workflows

The processes this workspace has defined, with their stages, who owns each and their service levels, seen from Builder's side. The work inside them happens in Workflows, and that is where a workflow is defined.

Records

What the workspace actually holds, counted by table rather than declared. It is worth reading before deciding a module is empty. The fields on each record type are fixed for now; custom fields per record type are not built.

What Builder does not do

  • It does not decide who sees what. Module access is set by department in Organisation › People & access › Module access. See Admin.
  • It does not route leads. Lead assignment moved to Organisation › Rules & Automation. See Organisation.
  • It does not choose the industry pack. That is set by Rople; see Workspace settings.

Common questions

Why is Builder not in my sidebar? It is offered only in the workspaces that run Rople itself while it is reworked.

Can I build a module without a workflow? You can save it as a draft. It cannot go live until it has a dataset, because a live module with nothing behind it would be an empty page in everybody's sidebar.

What seat floor should I set? The lowest seat that should be able to open it. Everybody means every seat.

Can I rename a module after it is live? Yes. The name is what the sidebar says and it also makes the address, so links people have already sent stop working.