Definition
When you want to share an app with your team, you need a way for colleagues to sign in without inventing a new password for every tool. That sign-in pattern is often called SSO, short for single sign-on. In plain English it is company login or team sign-in: each person proves who they are once, usually with your organisation’s identity provider or a passkey, and then opens the apps they are allowed to use. SSO is the door. Access control decides which rooms they can enter.
Why it matters
AI-built internal tools fail in the wild when sharing means “here is a public link” or “email me the HTML.” Finance and SME teams need to invite people by name, keep outsiders out, and avoid stuffing passwords into generated code. Company login moves identity out of the app and into the platform, which is safer and easier to audit when tools spread across a small business.
How Croft fits
Croft puts company login in front of the apps you host and share. You invite your people; they sign in once; you choose who can open which apps. Apps do not need to implement their own login flows. That is SSO in everyday terms, built for private vibe-coded tools rather than enterprise paperwork first.
Keep reading
FAQ
Frequently asked questions
What is SSO in plain English?
Company login. Your people sign in once with your organisation’s identity and then use the apps they are allowed to open.
Why lead with sharing the app, not with OAuth jargon?
Because the job is “let my team use this tool safely.” SSO is the name for the login pattern that makes that sharing work without a password pile.
Does Croft include company login for AI-built apps?
Yes. Every croft has team sign-in in front of apps so you can share privately without coding auth yourself.
Stake out your croft.
Your team's first app could be live before lunch.
Get your croft7 days free, no card to start. From $24/month - cancel anytime and take everything with you.