Makerbay Platform is the shared operating layer for your organisation. It connects people, roles, permission keys, enabled modules, and audit activity so teams can work in focused product spaces without losing context.
Rather than asking each module to maintain a separate user model, the Platform gives administrators one place to set responsibility and oversight before they enable the workspaces their teams need.
makerbay / platform
Overview
Members
Roles
Audit
Organisation control
Platform workspace
Members
Organisation context
Roles
Permission keys
Audit
Activity history
Identity and organisation
One workspace establishes the context for members, teams, and enabled modules.
Roles and permission keys
Administrators define responsibility through roles, grouped permission keys, and member assignments.
Audit and enablement
The Platform records important access activity and underpins new module enablement.
In the application
Implemented
Organisation workspace and member context
Role catalogue and custom-role creation
Permission keys grouped by module
User-to-role assignment
Administrator activity and data-change logs
Note — Role and permission changes are applied through the Platform; affected users may need to refresh or sign in again to receive the updated session context.
Access workflow
Step 1
Create or select the organisation workspace.
Step 2
Create a role and choose the permission keys it needs.
Step 3
Assign members to the role and refresh their session when access changes.
Step 4
Review important administrative activity in Audit Logs.
Platform FAQ
Who can manage roles and permissions?
Organisation administrators use the Platform role and permission experience to create roles, choose permission keys, and assign members.
When does an access change take effect?
Permission changes are applied through the Platform. Affected users may need to refresh or sign in again to receive updated session context.
Does every module need a separate user directory?
No. Enabled modules work from the same organisation and member context managed by the Platform.
HR brings the everyday people records, requests, reviews, and hiring workflows that teams need into a shared workspace.
Who it's for
For people teams, managers, and growing organisations.
Current application experience
The HR workspace currently brings people operations, attendance, recruitment, performance, training, and related HR administration into an organisation-scoped experience.
In the application
Implemented
Employee, organisation, and people records
Attendance, leave, payroll, and expenses entry points
Recruitment and public careers application flows
Performance, training, skills, policies, and compliance areas
HR module pages are available today. Summary counters shown in older dashboard surfaces are placeholders, so they are not presented here as live analytics.
End-to-end workflow
Step 1
Set up the people record and organisation context.
Step 2
Invite the people responsible for HR and manager work.
Step 3
Run attendance, leave, recruitment, or development activity in the appropriate module.
Step 4
Use the person and organisation context to follow up on the work.
Modules and features
Employee records and organisation structure
Leave requests and approvals
Attendance and work schedules
Performance reviews and goals
Recruitment workflows
Skills and development records
Concepts
People records
Keep employee profiles, teams, reporting lines, and working arrangements in the organisation context.
Requests and approvals
Route leave, attendance, and people-process decisions to the right people with clear ownership.
Growth and hiring
Coordinate performance, development, and recruitment work without separating it from the people record.
Roles (Platform-controlled)
Organisation administrator configures HR access.
HR administrators manage people records and policies.
Managers review their teams and act on assigned approvals.
Employees view and update the information available to their role.
Frequently asked questions
What HR work is available?
The current application includes people, attendance, leave, payroll, recruitment, performance, training, skills, policies, and compliance entry points.
Can candidates apply without an internal login?
The careers experience includes public application, referral, and offer-response paths for recruitment workflows.
Are dashboard figures live analytics?
HR module pages are available, but summary counters in older dashboard surfaces are placeholders and should not be read as live analytics.
CRM gives revenue-facing teams a shared view of leads, contacts, accounts, opportunities, and the work that moves a relationship forward.
Who it's for
For sales teams, account managers, and business development.
Current application experience
The CRM application currently supports leads, contacts, pipelines, follow-ups, activity history, and dashboard monitoring for customer work.
In the application
Partial implementation
Lead and contact workspaces
Sales pipeline and opportunity movement
Calls, emails, meetings, notes, and tasks
Date-range dashboard for pipeline value, follow-ups, owner activity, and win rate
CRM is in active development. The listed lead, contact, pipeline, follow-up, activity, and dashboard flows are present; broader scope continues to evolve.
End-to-end workflow
Step 1
Create a lead and record the first customer context.
Step 2
Add contacts, notes, and follow-up activity.
Step 3
Progress the relationship through the sales pipeline.
Step 4
Review follow-ups, stalled work, and ownership from the dashboard.
Modules and features
Lead and contact management
Account and relationship timelines
Deal pipelines and stage tracking
Activities, tasks, and follow-ups
Opportunity ownership and collaboration
Customer notes and shared context
Concepts
Relationship records
Capture people, organisations, and the connection between them as shared customer context.
Pipeline work
Move opportunities through defined stages with accountable owners and visible next steps.
Activity history
Keep meetings, notes, tasks, and changes with the relationship rather than in personal inboxes.
Roles (Platform-controlled)
Organisation administrators control CRM access.
Sales leads configure pipeline practices for their teams.
Account owners manage the relationships assigned to them.
Contributors record activities and work where their role permits.
Frequently asked questions
What does the CRM dashboard show?
It monitors leads, pipeline value, follow-ups, owner activity, win rate, and recent customer activity for the selected date range.
Can teams track customer follow-ups?
Yes. Lead and contact activity can be connected to follow-up work, with overdue and upcoming follow-up context in the dashboard.
Why is CRM marked partial implementation?
Lead, contact, pipeline, follow-up, activity, and dashboard workflows are available while the broader CRM experience continues to evolve.
Finance is intended to connect invoices, expenses, budgets, approvals, and operational reporting in a controlled financial workspace.
Who it's for
For finance teams, operations leaders, and approvers.
Current application experience
Finance capabilities are currently delivered through organisation-scoped operational modules, including vendor bills, payments, approvals, invoices, expenses, budgets, and reporting entry points.
In the application
Partial implementation
Accounts Payable for vendor bills, payments, and approvals
Accounts Receivable and invoicing routes
Expenses, procurement, vendors, budgets, cost tracking, and reports
Finance is in progress: several finance modules are available, while a single consolidated finance workspace is still being developed.
End-to-end workflow
Step 1
Capture or manage a vendor bill or other financial record.
Step 2
Route the item through the relevant payment or approval work.
Step 3
Use the related finance module to continue invoicing, expense, or budget work.
Step 4
Review the financial context from the appropriate operational report.
Modules and features
Invoices and billing workflows
Expense capture and review
Budgets and spend visibility
Approval-ready financial records
Customer and supplier transaction context
Reporting for operational decisions
Concepts
Financial records
Bring invoices, expenses, and supporting context into a consistent operational record.
Controlled approvals
Use Platform roles to ensure the right people can submit, review, and approve financial work.
Decision context
Connect spend and billing activity to the teams, customers, or projects that need visibility.
Roles (Platform-controlled)
Organisation administrators set access boundaries.
Finance administrators manage financial records and operational views.
Approvers act on records assigned to their approval role.
Contributors submit and follow the financial work available to them.
Frequently asked questions
Which finance operations are available today?
Makerbay includes organisation-scoped routes for vendor bills, payments, approvals, invoices, expenses, budgets, procurement, vendors, cost tracking, and reports.
Is there one consolidated finance home?
Finance is being developed as a connected experience. Current capability is delivered through the individual operational modules.
How are approvals controlled?
Finance activity uses the shared Platform access model so contributors, reviewers, and approvers can be assigned appropriate responsibility.
Productivity helps teams plan and deliver work through issues, projects, boards, saved views, My Issues, and an inbox for updates.
Who it's for
For product, engineering, operations, and delivery teams.
Current application experience
Productivity is an issue-first workspace with project context, configurable workflow states, list and board views, saved filters, My Issues, Inbox, and bulk work actions.
In the application
Implemented
Issues with project, label, priority, and assignee context
List and board layouts with URL-persisted filters and grouping
Workflow-state movement with optimistic updates
Bulk status, assignee, and label actions
My Issues, Inbox, project, label, and workflow settings
End-to-end workflow
Step 1
Create or assign an issue in the relevant project.
Step 2
Use list or board view to filter, group, and plan the work.
Step 3
Move work through the configured project workflow states.
Step 4
Follow assignments and mentions through My Issues and Inbox.
Modules and features
Issues with ownership and priority
Projects with milestones and progress
Boards and tailored work views
A personal My Issues workspace
Inbox for updates and mentions
Team collaboration around the work
Concepts
Issues
A single unit of work with clear ownership, priority, status, and supporting conversation.
Projects and views
Organise related work into projects, then use boards and views that match how each team plans.
Personal attention
My Issues and inbox bring assigned work, mentions, and changes into a focused daily workspace.
Roles (Platform-controlled)
Organisation administrators enable access for the right teams.
Project leads manage project structure and team views.
Contributors create and progress issues within their workspace.
Observers can follow the work where their Platform role allows.
Frequently asked questions
Can teams choose between list and board views?
Yes. Issues support list and board layouts, with filters, search, and grouping persisted in the URL for shareable work context.
How do workflow changes work?
Teams move issues through default or project-specific workflow states. The application updates optimistically and restores state if a change fails.
What is My Issues for?
My Issues and Inbox give contributors a focused place to follow assignments, updates, and mentions across their work.
Customer Service is intended to give support and success teams a clear workspace for tickets, customer feedback, queues, handoffs, and service history.
Who it's for
For support teams, customer success, and service leaders.
Current application experience
Customer Service currently provides an authenticated support-ticket workspace alongside related feedback, portal, knowledge-base, onboarding, and analytics entry points.
In the application
Partial implementation
Dedicated support-ticket manager
Ticket and feedback entry points
Customer portal, knowledge-base, onboarding, and analytics areas
Customer Service is in progress. A protected ticket workspace is available; broader queue, escalation, and service-history behaviour is still evolving.
End-to-end workflow
Step 1
Open the support-ticket workspace from the organisation context.
Step 2
Triage the customer request and capture the relevant support context.
Step 3
Use related feedback or customer areas when the work requires them.
Step 4
Keep the request history connected to the customer conversation.
Modules and features
Ticket intake and assignment
Customer feedback capture
Service queues and ownership
Status updates and internal notes
Support history by customer
Escalation-ready issue tracking
Concepts
Service tickets
Track a customer question or issue from intake through assignment, resolution, and follow-up.
Queues and ownership
Make workload and responsibility visible so teams can coordinate service without losing handoffs.
Customer context
Keep support history and internal notes connected to the customer relationship.
E-learning is planned as a role-aware learning workspace for courses, learning paths, assignments, assessments, and completion evidence.
Who it's for
For learning teams, enablement leaders, and people managers.
Planned product direction
E-learning is planned as a role-aware learning experience. Current application entry points include My Learning, courses, content, learning, quizzes, and analytics routes.
Planned module areas
Planned
My Learning entry point
Course and content route surfaces
Learning, quiz, and analytics route surfaces
Planned learning paths, assignments, assessment, and completion evidence
The current route surface establishes the learning experience entry points; course authoring, assessment persistence, and certificate behaviour remain planned.
Intended workflow
Step 1
Learning administrators structure a course or learning path.
Step 2
Managers assign the experience to the appropriate learners.
Step 3
Learners complete content and assessment work.
Step 4
Managers review intended progress and completion evidence.
Modules and features
Course and lesson management
Learning paths by role or team
Assessments and completion records
Certificates and compliance evidence
Learner progress tracking
Training assignment and reminders
Concepts
Learning content
Structure courses and lessons so learning teams can publish clear, reusable programmes.
Paths and assignments
Assign learning by role, team, or need while keeping the learner’s work in one place.
Evidence of progress
Capture assessment outcomes, completion, certificates, and compliance records as intended learning evidence.
Roles (Platform-controlled)
Organisation administrators set product access.
Learning administrators publish content and manage programmes.
Managers assign learning and review their teams’ progress.
Learners complete the content made available to their role.
Frequently asked questions
What learning areas exist today?
Current application entry points include My Learning, courses, content, learning, quizzes, and analytics routes.
Can teams rely on certificates and assessments today?
The route surface is in place, while course authoring, assessment persistence, completion evidence, and certificates remain planned.
How will access work?
The intended experience uses Platform roles so learning administrators, managers, and learners receive the right access for their responsibilities.
SmartID is planned to connect identity profiles, organisation-aware credentials, verification workflows, access context, and identity activity records.
Who it's for
For organisations managing identity, access, and verification workflows.
Current application experience
SmartID currently provides an entitlement-aware hand-off from Makerbay into an enabled identity experience without requiring a second sign-in.
In the application
Partial implementation
Organisation module-entitlement check
Short-lived signed-in hand-off with user and organisation context
Protected access that redirects unavailable organisations appropriately
Planned native identity, credential, and verification workspaces
Makerbay currently provides the authenticated hand-off. Native identity profile, credential, verification, and activity-management screens are planned.
End-to-end workflow
Step 1
An authorised user opens SmartID from an enabled organisation.
Step 2
Makerbay validates the organisation entitlement.
Step 3
Makerbay creates a short-lived hand-off context.
Step 4
The user continues into the configured SmartID experience.
Modules and features
Secure identity profiles
Organisation-aware credentials
Role-based access context
Verification workflow support
Credential status visibility
Identity activity records
Concepts
Identity profiles
Maintain a trusted identity profile connected to the person and organisation that uses it.
Credentials and verification
Manage credential status and verification steps with clear states and responsible reviewers.
Authorised context
Connect trusted identity information to Platform-controlled roles and the work a person may perform.
Roles (Platform-controlled)
Organisation administrators control identity access.
Identity administrators manage verification workflows and credential states.
Reviewers assess the verification work assigned to them.
Users see identity information and actions available to their role.
Frequently asked questions
What does SmartID do today?
Makerbay validates that the organisation has SmartID enabled, then creates a short-lived signed-in hand-off into the configured identity experience.
Does SmartID have a native credential workspace yet?
Native identity profiles, credentials, verification, and activity-management screens are planned; the current implementation is the secure hand-off.
Why might a user not be able to open SmartID?
The organisation must have the SmartID module enabled. Unavailable organisations are guided away from the enabled experience.
Skilium connects staffing plans, projects, timesheets, and invoices so client delivery teams can manage capacity and commercial work in one place.
Who it's for
For staffing teams, delivery leads, project managers, and client services.
Current application experience
Skilium currently provides organisation-scoped staffing operations for candidates, client requests, assignments, status decisions, filters, and export.
In the application
Implemented
Candidate records with employment and skills information
Client requests and candidate-to-request assignments
Shortlisted, selected, rejected, and hold assignment states
Status filters, permission-aware actions, and CSV export
Broader projects, timesheets, and invoices delivery scope
The staffing workflow is available today. Projects, timesheets, and invoices remain part of Skilium’s broader delivery scope and are documented as rollout capabilities.
End-to-end workflow
Step 1
Add a candidate and capture the relevant skills or employment context.
Step 2
Choose a client request and create the staffing assignment.
Step 3
Shortlist, select, reject, or hold the assignment as the delivery decision changes.
Step 4
Use filters and export to coordinate the current staffing picture.
Modules and features
Staffing plans and resource assignments
Projects, milestones, and delivery status
Timesheets and approval workflows
Invoices linked to project work
Resource availability and utilisation context
Client delivery and project financial views
Concepts
Staffing plans
Match people and capacity to client work with a clear view of assignments and availability.
Project delivery
Track projects, milestones, delivery status, and the work that supports client outcomes.
Time to invoice
Connect approved timesheets to project context and invoicing work rather than managing them in isolation.
Screen View is planned for consent-aware screen sessions that give remote support and collaboration teams controlled visibility, clear participant states, and session records.
Who it's for
For support teams, operations teams, and distributed collaborators.
Planned product direction
Screen View is planned for consent-aware remote assistance and collaboration sessions with clear participant states and controlled access.
Planned module areas
Planned
Planned session request and participant invitation
Planned consent and access-state confirmation
Planned live troubleshooting context and hand-off support
Planned session activity record
No Screen View implementation has been released in the current application. This section describes the planned experience only.
Intended workflow
Step 1
A coordinator starts a support or operations session request.
Step 2
Participants confirm consent and allowed session access.
Step 3
Authorised people collaborate on the live issue context.
Step 4
The session closes with the intended activity record.
Modules and features
Remote screen-session visibility
Assistance and troubleshooting context
Controlled participant access
Session activity records
Clear consent and access states
Collaboration handoff support
Concepts
Controlled sessions
Start a session with explicit participant and access states rather than ambiguous remote visibility.
Support context
Give support and operations teams the screen context needed to collaborate on troubleshooting or handoff.
Session records
Maintain an intended activity record of important session events within the Platform audit model.
Roles (Platform-controlled)
Organisation administrators control Screen View access.
Session coordinators start and manage appropriate support sessions.
Participants control their consent and session state.
Authorised support users access sessions according to their Platform role.
Frequently asked questions
Is Screen View available today?
No. Screen View is planned and no released session-management implementation is documented in the current application.
What is the planned experience?
The intended product supports consent-aware requests, participant access states, remote assistance context, and session activity records.
How will access be controlled?
Screen View is designed to use Platform-controlled roles and explicit participant consent before authorised users access a session.
