Multi-tenant company onboarding
Onboard every company through one approved, auditable workflow.
LensyOS turns an onboarding template into a board of assigned activities. Work is submitted with its documents, approved by the Company Admin or the CEO, and the next activities unlock only when what they depend on is complete. Then targets and KPIs take over.
There is no public sign-up — your Company Admin creates your account and sends your login ID.
Brand & Marketing Onboarding
Onboarding board
Onboarding
ONB01
Client welcome and project kick-off
ONB02
Project scope and timeline approval
Discovery & Research
DSC01
Stakeholder discovery workshop
DSC04
Competitor analysis
- onboarding templates
2 onboarding templates
Brand & Marketing · Company Setup & Compliance
- activities in 24 phases
229 activities in 24 phases
in the Brand & Marketing template
- permissions
10 permissions
resolved from a person’s role on every request
- approval completes work
1 approval completes work
from the Company Admin or the CEO
Product
Everything onboarding needs, in one place
From the first kick-off call to recurring KPIs — each company works in its own space, under its own roles.
Onboarding board
Phases as columns, activities as cards. Locks come from each activity’s dependencies — never from where a card sits. My Activities shows just your work.
Activity pages
Fields, document uploads, comments and the review trail for every activity. Reassign it, and the comments travel with the work.
Approvals
One queue for onboarding submissions and targets. Approve, or request a correction; a stale approval is rejected.
Targets
Weekly, monthly and yearly targets set by managers and approved by the Company Admin or the CEO — rejected ones can be resubmitted.
Performance & reports
Actuals and evidence for Marketing, Sales and Finance measures. A figure nobody supplied reads “Data unavailable” — never a silent zero.
People, roles & permissions
One company and one role per person. Build custom roles from ten permissions, for the whole company or a single department.
Notifications & email
In-app notifications and email through a transactional outbox, so a failed email never undoes the work that triggered it.
Complete history
Who did what, and when, across the company — kept even after a company is deleted.
How it works
Four steps, with the rules built in
Order on the board is visual only. What can be worked on next is computed from the dependencies between activities.
- 1
Configure
The Company Admin picks the template that fits the company and tunes its requirements, fields and predecessors.
- 2
Assign
Hand out a single activity, a set of them, a whole phase or the entire board. Assignment says who is responsible; the role says what they may see and do.
- 3
Submit
The assignee fills in the details, uploads the documents and submits the activity for review.
- 4
Approve & unlock
The Company Admin or the CEO approves — never the position that submitted. Completed work unlocks every activity that was waiting on it.
When all required scope is complete, the Company Admin closes the onboarding — and the company carries on with targets and performance tracking.
Roles
Clear responsibility at every level
Each person belongs to one company and holds one role. Seeing the board never grants the right to edit or approve.
Super Admin
PlatformRuns the platform — companies, SMTP, email templates and maintenance — and works inside a company by opening its workspace.
Company Admin
One per companyOwns the company: people, roles, departments, the onboarding configuration and its final closure. Approves onboarding and targets.
CEO
At most one activeApproves onboarding work and targets, and can set targets.
Manager
ManySets targets for approval and works the activities assigned to them.
Department Head
Per departmentCreates custom roles inside their own department.
Custom roles
UnlimitedAny mix of the ten permissions, company-wide or scoped to one department.
Security
Built so one company never sees another’s
Hiding a button is not access control. In LensyOS every decision about who may see or change something is made on the server, against the database.
- Tenant isolation is enforced on the server: every read and write is filtered by the company resolved from your session, never by an id the browser sends.
- Every action is authorised on the server, then checked again by the service behind it.
- Submissions and approvals run in a transaction with a row lock — one decision per reviewer per submission.
- Sessions live in the database and end after 8 hours idle, or 7 days at most.
- Repeated failed sign-ins are throttled and locked out; the Super Admin can clear a lockout.
- Raw error text never reaches the browser.
Pick up where your team left off
Sign in with the login ID (email) and password you received.