Tenant setup and invitations
Define the order in which an admin creates sites, assigns roles and invites staff.
Design the first usable session for a customer managing several sites. GreyBath helps product teams decide what a tenant admin, site manager and invited colleague need to complete on day one.
Explore what we build
01 / What we build
Define the order in which an admin creates sites, assigns roles and invites staff.
Show accepted, unresolved and duplicate rows with a correction path that retains the valid records.
Identify the events that mark a usable tenant and cover empty, invited and incomplete states.
City context, honestly stated
For projects in Navi Mumbai, a product team near Airoli building operations software may sell to a customer with a central admin and separate locations. Design the setup journey with both shared defaults and site-level responsibilities in view. GreyBath delivers through remote workshops, reviews and handover.
A customer creates a tenant for three storage sites and uploads an inventory CSV. Two rows have the same item reference at different sites, while a third row names a site the admin has yet to create. The import preview shows the two valid records under their sites and asks the admin how to handle the unresolved row. A site manager joins by invitation and sees only the assigned site. The prototype test checks whether the admin can finish the valid portion, return to the unresolved row and explain what the site manager can access.
Where it fits
Bring the people who use, review and maintain the first release into the scope discussion.
Decide which configuration steps are necessary for the first customer to begin using the product.
Reduce setup calls by showing which tenant tasks remain open and who owns them.
How we work
Agree the activity that proves a site can begin work and which roles take part.
Test import review alongside inviting a restricted site manager.
Ask users to identify their scope and recover one unresolved row without creating duplicates.
The proposal sets the first workflow, delivery responsibilities and the evidence needed before rollout.
Discuss your projectBring a simple permission grid and a list of the records shared across sites.
Use a small redacted import file with one duplicate and one row that needs a decision.
Yes. We can test a specific onboarding flow with current terms, roles and existing data constraints.
Redacted samples or invented records that reflect the validation cases are enough for design and testing.
Define a completed setup event and track how many users can reach it, how long it takes and which unresolved tasks require support.
Start with one workflow