Railbase
Browse documentation
GPTClaude

THE RAILBASE PRODUCT GUIDE

Prepare the company, people and evidence

Set up Acme's company context and separate installation access, everyday work and decision authority.

Updated

One case throughout the course

Acme Workshops is a fictional company. In October 2026 it buys a machine from Aster Equipment for $6,000 to deliver a $9,000 customer project. Its project budget is $10,000: equipment $6,000, payroll $2,000 and reserve $2,000. Opening bank funds are $20,000. All amounts are USD; training documents use zero tax to keep the arithmetic visible. This is a training assumption, not a tax exemption.

Core establishes the company, people, documents and authority. Accounting follows this purchase to financial close. GRC examines the same supplier, decisions and evidence. You do not create a new company for each lesson. These records are an exercise to prepare in a training company, not a promise that the public demo is preloaded with this case.

Role and prerequisites

The installation operator has completed installation. An authorised company administrator prepares company access. Requester, independent reviewers and financial specialists use their own identities. Installation administration alone grants none of these company jobs.

Prepare Acme

  1. Check the operator-provided licensed Acme training company before inviting people. For production, connect your actual verified legal company and Product through the supported Account pairing flow; do not submit the fictional course identity for verification.
  2. Invite Tom, the purchase requester; Maya, the controller; Leo, the payment preparer; and Eva, the independent reviewer. Assign the required company roles and effective positions through the governed access process. Do not give everybody all permissions.
  3. Establish the responsible positions and approved authority for requests, payments and policy publication. A role and a position are separate prerequisites; an approval needs the assigned object as well.
  4. Put Aster's quotation and the project justification in Core Documents, retaining the exact versions. Use business names in selectors rather than copying technical identifiers.
  5. Sign in separately as Tom and Eva. Verify their company membership and visible work; test a person without Acme access.

Verify the saved result

Reopen the company: memberships and dated position assignments remain. Tom can prepare his own work; Eva sees only assigned reviews. Neither obtains installation authority from a company role. If a required position or eligible reviewer is absent, complete that prerequisite before publishing the route.

Next, configure authority and delegation. The practice case uses independent budget and controller decisions for the $6,000 purchase; these are Acme's approved rules, not universal Railbase defaults.

Was this page helpful?Thanks for your feedback!