Skip to content

What is Beezr?

Concept6 minFoundation

Beezr has two sides. In Designer space you describe your business: what you keep track of, what people fill in, what happens next. In App space your colleagues do the work. What you build in the first appears in the second.

The Modules page in Designer space, with the Designer and App switch in the top bar and one card for each module.
    The Designer | App switch moves between the two sides. App opens App space in a new tab.
    Add module creates a new kind of record to keep.
    Each card is a module. Opening it shows its fields, forms, views and automation.

How do the two sides relate?

Section titled “How do the two sides relate?”

Designer space is for the people who build the system. It has the pages for modules, fields, forms, views, workflows and security.

App space is for everyone else. It shows the applications you published, with their menus, lists, records and tasks. Layla can build in Designer space while Omar approves a request in App space. Both work on the same module.

The company’s environment is called a workspaceWorkspaceThe company's Beezr environment (name shown in the top bar).Open glossary ↗. Its name sits in the top bar of Designer space.

What is an application made of?

Section titled “What is an application made of?”

An applicationApplicationA named menu of modules (grouped into sections) that people open in App space.Open glossary ↗ is a menu. It groups modulesModuleA table of business data (for example Customers) with fields, forms, views and automation.Open glossary ↗ into sections, so people find Contracts under Purchasing, not in a list of 40 things. The application owns nothing else. Records, fields and workflows live in the modules.

  1. Application
  2. Module
  3. Fields
  4. Records

A module is one kind of record: Contracts, Vendors, Equipment Requests. Each recordRecordOne row of a module.Open glossary ↗ is one item of that kind, such as contract CONTR-00003. A record’s information is split into fieldsFieldA column of a module with a type, label and system name.Open glossary ↗: a contract number, an end date, a status. Every field has a type that decides what it accepts, such as Text, Date or Lookup.

Three more pieces decide how people fill in and see a module:

PartWhat it doesWhere you build it
FormThe page people fill in to create or edit a recordForms
Data viewHow people browse many records: table, Kanban board, calendar and moreDataviews
Smart viewThe designed page for one record: header, action buttons, related tabsSmart views

A lookupLookupA reusable list of choices for Lookup and Multi Select Lookup fields.Open glossary ↗ is a reusable list of values, like the statuses a contract can have. A field of type Lookup lets people pick from it. Because every record uses the same values, a Kanban board can group cards by status.

A contract record in App space, with the application menu on the left, the header, action buttons and tabs at the top, and the fields below.
    The menu comes from the application: groups, then modules.
    The header shows the record’s title, status and key facts. The smart view designs it.
    Action buttons run workflows, such as Publish Draft.
    Details, Notes, Attachments and related records sit in tabs.
    The fields appear in the sections the builder arranged.

What does a workflow do?

Section titled “What does a workflow do?”

A workflowWorkflowAn automation: trigger plus steps, run per module; also called "flow" on the home page.Open glossary ↗ does work for people. It starts with a triggerTriggerWhat starts a workflow: record created/updated/created or updated/deleted, Adhoc, or webhook.Open glossary ↗, such as “a record is created”, and then runs steps: ask for approval, update a record, send an email, branch on a value.

  1. Request created
  2. Approval task
  3. Approved: update status
  4. Rejected: send email

The Approval task step pauses the workflow until someone decides. Then it continues on the Approved path or the Rejected path.

A workflow drawn in the Designer: a trigger, an Approval task, and two paths that each end in a Record manager step.
    The trigger says what starts the workflow.
    An Approval task pauses the run until someone decides.
    The Rejected and Approved paths each lead to their own steps.
    A Record manager step changes a record, for example its status.

Who can see and do what?

Section titled “Who can see and do what?”

People sign in and see only what their role allows. A permission profile lists which applications a role can open, which modules and fields it shows, and which actions it allows. You manage users, roles and permissions under Account settings › Users & Security.

Where do I start?

Section titled “Where do I start?”

Build something small. The Quickstart takes you through an Equipment requests app, from the first module to your first request. If you want to look around first, A tour of the Designer names every part of the screen.

Check yourself

Layla builds a Contracts module in Designer space. Where do her colleagues work with contracts?
Show the answer

In App space, through an application that lists the module. Designer space is where people build. App space is where people use what was built, through applications that list modules.

What does one module hold?
Show the answer

One kind of record, such as Contracts. A module holds one kind of record. An application groups several modules into a menu.

What starts a workflow?
Show the answer

A trigger, such as a record being created. Every workflow begins with a trigger. The steps after it do the work.

What's next

Build your first appBuild an Equipment requests app from an empty workspace in about 15 minutes, with a form and a list, then add your first request in App space.A tour of the DesignerFind your way around the Designer: the left rail, the top bar, the module island, Jump to, Help and the home page.

Last checked