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. That is deliberate: a workflow is already a table with fields, records, owner sections and five ways of looking at them, so a module built here gets the table, the board, the calendar, the gallery, the service level clock and the workflow to KPI generator without any of it being written twice.
A module lives at its own address, /w/m/ followed by its slug, and it has three states:
- Draft. Saved and listed in Builder, openable at its own address by anybody whose seat clears the floor, and deliberately absent from every sidebar including its author's. A half defined module in the navigation is how a colleague finds an empty screen and decides the product is broken.
- Live. In the sidebar, for every seat at or above the floor. A module cannot go live without a dataset, and the API says so rather than letting it.
- Retired. The definition and its records are kept, the route is closed. A link somebody saved last quarter stops opening rather than opening something the workspace has withdrawn.
Deleting a module removes the definition and leaves the workflow, which stays reachable in the Workflows module. Removing both in one press is the version of this that nobody can undo.
Rules
What this workspace enforces, read out of the code that enforces 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, and that is the only version of the claim that cannot go stale.
Lead assignment
How new leads are routed, configured here rather than in Leads, because "how does this company route its leads" is a decision two people make occasionally and "here are today's leads" is what everybody does all day.
Rules are evaluated in order and the first match wins, so the order is the configuration. Moving a rule up or down is a first class action rather than a detail of editing one.
Workflows
The processes this workspace has defined, from Builder's side. The work inside them happens in the Workflows module.
Records
What the workspace actually holds, counted by table. It is the answer to "how much is in here", and it is worth reading before deciding a module is empty.
What Builder does not do
It does not decide who sees what. Module access is a question about departments and it is answered in Admin, under Module access.
How it connects
- A module defined here appears in the sidebar and opens the workflow behind it.
- Lead routing changes what happens in Leads and pipeline.
- Who may open a module is set in Admin.
Common questions
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 is a broken page in everybody's sidebar.
What seat floor should I set? The lowest seat that should be able to open it. A floor of 1 means everybody.
Can I rename a module after it is live? Yes. The slug is its address, so changing that changes the link. The name is what the sidebar says.