Getting started
First steps for opening Axalot docs and preparing a workspace for product work.
Getting started
Start with the workspace context before changing product settings. Most Axalot console data belongs to the currently active organization, so the first check is always which organization is selected.
After account creation
A Axalot user account is personal. Product data lives in organizations. After signing up, choose the organization path that matches how you will work.
Create an organization when you are setting up your own company workspace or need to manage Tracker/META data yourself. The creator becomes an Active Admin of that organization.
If you do not need your own Tracker workspace, create only your personal account and ask an Admin or TeamLead from the target organization to invite you. After accepting the invite, you work inside that company's organization.
Account and organization are separate
Creating a user account does not automatically create product data. Tracker and META records appear only inside the active organization.
Open Console / Organizations.
Create an organization if this is your company workspace, or accept an invitation if another company already manages the workspace.
Confirm the organization you want to work in is marked as current.
Check your role. Admins and TeamLeads can manage organization access; Members use the enabled product modules.
Open the docs space that matches the task: General for workspace access, Tracker for tracking operations, META for META assets and accounts.
Use search when you know the object name but not the section. Search covers all public docs pages.
Organization first
If a console table looks empty, confirm the active organization before debugging the product feature. Switching organizations changes the data loaded in the console.