How LegionEdge works
Your organization, your IAM. We run the platform around it.
LegionEdge approves every organization before it exists. Once you’re in, you run your own identity and access, see support sessions while they run and end them, and share documents with outsiders on your terms.
Request access and approval
Nothing is created until it’s approved.
An organization on LegionEdge starts as a request, not an account. Until a LegionEdge administrator approves it, a request creates no organization, no sign-in and no session.
Own your IAM
Your organization runs its own identity and access.
As owner you hold your organization’s identity and access: people, roles, policies, single sign-on, directory sync and audit, all from the IAM console. LegionEdge sets the outer limits of your plan, as a boundary you can read.
Single sign-on
Connect your identity provider over SAML or OIDC, so your people sign in with the accounts they already have.
Directory sync
Keep members and groups in step with your identity provider over SCIM, with a bearer token you can rotate.
Roles and policies
Build roles from the actions they allow, write policies with conditions, and simulate who can do what before you change anything.
Members, groups and teams
Invite people, organize them into groups and teams, and see each person’s access and sessions.
Sign-in policy
Decide who must use a second factor, such as an authenticator app or a passkey, and set the password rules for your organization.
Audit log
Changes are recorded in a hash-chained log that you can filter, verify and export.
Delegated administration
Hand parts of administration to others through authorities, each with a ceiling on what its holder can grant.
Your plan’s limits, in the open
What your plan allows is a permission boundary you can read, with a tester that tells you whether an action falls inside it.
Support access you control
You can see support access, and you can stop it.
Access into your organization through a trust runs as one of your own roles, its sessions are listed in your console while they’re live, and you can end them. What happens in them is in your audit log.
Data rooms
Share documents outside your organization, on your terms.
Data rooms bring guests in to see exactly what you share, under permissions you set, with a record of what they do.
Guests see only their rooms
People you bring in from outside get a view with only the rooms shared with them: no other products, no billing and no IAM.
An NDA before entry
When a room has an NDA, guests accept it the first time they open the room.
Permissions by folder and document
A permission matrix sets what each group or person can do with every folder and document, and explains why someone has access.
Controlled documents
Documents keep their versions, can be marked view-only, and are watermarked when downloaded.
Questions and answers
Guests ask questions in the room. Your team assigns them, approves the answers and publishes them.
Activity you can verify
Views and downloads go into a hash-chained activity log that you can verify and export.
Designed, and on its way.
These are specified and being built, but not yet available. They move up into the sections above as they ship.