Trial onboarding guide

Choose Request a Trial Account on the sign-in page to read this guide, then continue to the request form. Enter your full name, work email address, Company name and audit operating model. Choose Internal & supplier audits when you audit your own organisation or its suppliers, or Audits on behalf of clients when you provide audit services to Clients. Add any information that will help us understand your evaluation.

Submitting the form sends an enquiry only. It does not create a user account, a Company workspace or immediate access. RASCIbase reviews each request manually.

After approval, RASCIbase prepares your Company workspace and sends an administrator invitation to the named requester. Open the invitation email, follow its account-setup link, enter your full name and choose your password. The invitation must be prepared before account registration; colleagues cannot join by registering themselves.

The trial review date is normally about one month after activation. It is a manual review reminder, not an automatic access expiry or deletion date. RASCIbase will discuss the evaluation, an extension, a licence agreement or closure with you. When a licence agreement is recorded, the trial date is cleared and the Onboarding Guide card disappears from Home. The guide remains available under Help → Onboarding.

Sign in as the Company Administrator and start on Home. The module list shows only modules enabled for your Company and available to your user account. Use Settings & users → General to review the Company profile, logo, welcome message and standard document footer used by generated reports.

Set up shared Company information before detailed module work where relevant:

• Projects: maintain the optional Company Project register from Home. Projects can provide shared context for AUDIT, ACTION and INSPECT; they do not have to be applied to every record.
• External parties: register Suppliers, Clients where applicable, and other third-party organisations from Home.
• Disciplines: Company Administrators maintain the shared Discipline list used by modules such as ACTION.
• Company identity: use Company for your own organisation, Client only for organisations receiving audit services from an audit-service Company, and Auditee for the supplier, site or unit being audited.

Your audit operating model determines whether the optional Client grouping is relevant. Keep shared registers consistent rather than creating separate copies in each module. If you belong to more than one Company, select the intended Company before adding or changing records; each Company has its own workspace and access.

Existing Company users join by administrator invitation. Open Settings & users → Users & access, invite each person by email and select their Company Administrator status and module access deliberately. A new invitation starts with no module access, so choose at least one module or make the person a Company Administrator before sending it.

Company Administrator rights and module roles are assigned independently for each Company. A person may belong to several Companies with different responsibilities in each. Enabled Company modules remain the outer boundary: assigning a module role does not enable a module that the Company does not have.

For AUDIT, check the linked Auditor register as well as user access so the right people can be assigned to audit teams. For PROCESS, use Viewer, Editor or Administrator access as appropriate. ACTION access is assigned separately. INSPECT can also use Project-specific PRE, Inspector and Read only assignments when the Company Administrator activates Project-restricted access.

Pending invitations can be reviewed and reminded from Users & access. Use the account menu to choose Open at sign-in when more than one module is available. This is a personal starting-page preference, not a permission.

Project-aware access across the whole suite is still being designed. Do not assume that assigning someone to a Project currently restricts every ACTION or other module record to that Project; review the access granted before adding sensitive information.

Use a small, realistic evaluation scenario and involve the people who will perform each role.

• AUDIT: review workflow settings, prepare or adopt a checklist, register an Auditee and team, then plan an audit. Try checklist answers, comments, evidence and findings before review, approval and report generation.
• ACTION: configure Sources and Disciplines, create an Action and follow its response and verification. Create a meeting series with its default participants, then create a meeting and review its agenda, attendance, minutes and Action log. My actions is the default register view; other views are selected deliberately.
• PROCESS: configure Value Streams and Linked Item Types, then review or create Roles, Linked Items, Process Groups and Processes. Open a Matrix to review tasks and RASCI assignments, and try the register print and spreadsheet outputs.
• INSPECT: where enabled, prepare Projects, Suppliers and Tags, then try an ITP and its checkpoints. Add Project roles if restricted access is used, and evaluate inspection evidence, review and punch follow-up where relevant to your work.

Use Help for role guidance, the Onboarding section and FAQs. The Assistant answers from maintained Help articles and records you are permitted to access; questions not covered are recorded rather than guessed.

Company records are separated by Company access controls. Upload only information you are authorised to use, and request the current security documentation before adding sensitive production data. AI-assisted features are available only where enabled and produce suggestions for review, not automatic approvals. Share questions, unexpected behaviour and evaluation feedback with RASCIbase before the manual trial review.