Working in Bike · An app and its sheets

Working in Bike

An app and its sheets

Each part of the work is an app, such as Customer contracts, Hiring or Spend.

Sheets

Lists of rows, each with its questions (columns). A sheet can be a plain list, a document with lines (a bill and its items), an allocation (payments split across bills), a tree, whose rows sit under each other (cost centres, categories, classes and their sections), at most 8 levels deep, a ledger, whose entries are only added and add up to a balance (leave, stock moves, fee dues), or kept by date, whose values each start on a date and last until the next (price lists, salaries, spending limits, fee structures by year).

An app has at most 6 sheets.

Questions

At most 40 on a sheet. A question can be required, have a default ("whoever adds it", today, a fixed value, a formula, or a value from the row it links to: a candidate's hiring manager from its opening, filled when the row is added), or be computed from others.

Steps

A row moves through a sheet's steps (Draft → Signed → Active → Renewed or Ended). At most 6 steps before the end steps.

Rules

What happens by itself, at most 20 in an app. A rule never runs another rule more than 3 deep, and a rule that would set off itself is refused.

Roles

Who can see and do what. A role is people named one by one, everyone a person question names (say, every contract's Owner), or everyone.

It can see, add, edit, delete, move rows through steps and change how the app works, on every row, only their own rows, or their team's.

Connections

A rule can start or update a row in another app (a hired candidate starts an onboarding plan).