Overview
The LegionEdge consoles now share one address, cloud.legionedge.ai. This guide walks through everything between requesting an account and giving your first service its own API key, using only what’s in the console today.
A LegionEdge account is an organization: your own tenant, with its own members, roles, sign-in rules and audit log. You can’t create one yourself. You request it, and LegionEdge reviews the request. Until it’s approved, a request has no tenant, no identity and no session.
1. Request an organization
Open cloud.legionedge.ai/iam/signup, or use Request access on this site. The request has three short steps. You asks for your name, work email and country. Organization asks for your company or team, its account alias, company size, website and preferred region. Plan and products asks for a plan, the products you’re interested in, your use case and anything else we should know.
Choose the account alias with care. It’s the short name your colleagues enter when they sign in, and it appears in every console URL, as in cloud.legionedge.ai/acme. Aliases use lowercase letters, digits and inner dashes, up to 63 characters, and the form checks availability as you type. A few aliases are reserved because they would collide with the console’s own paths. Plans that aren’t self-serve go through our sales team, and the form tells you where to write.
2. Accept your owner invitation
A LegionEdge platform administrator reviews your request. When they approve it, your organization is created and its owner, usually the person who made the request, gets an invitation email.
Follow the link, choose a password, and you’re signed in as the owner. Invitation links expire. If yours has lapsed, contact us and we’ll send a new one.
3. Finish onboarding
Next, the IAM app walks you through onboarding, one step at a time. Administrators see the workspace setup steps first, then everyone sees their own. You can skip a step for now, or choose Finish later to go straight to the console. While a required step is still open, signing in brings you back to onboarding.
LegionEdge verifies some setup tasks. If one is sent back, you’ll see the reviewer’s note next to it.
4. Find your way around
Sign in at cloud.legionedge.ai/iam/login with your account alias, email and password. Your console is at cloud.legionedge.ai/<your-alias>.
The sidebar starts with Console home, Projects and Resources. Under Manage are Billing & Cost, Logs & Monitoring, Identity & Access and Secrets. Further down you’ll find Compute (volumes, launch templates, schedules, regions), Security & access (SSH keys, firewall), Operations (notifications, advisor, service health) and Governance (quotas and limits, labels, activity). The Service catalog lists LegionEdge products, and Support is where you open and follow cases.
5. Bring in your team
Identity & Access opens your organization’s IAM dashboard at cloud.legionedge.ai/iam/<your-alias>. In Directory, go to Members and choose Invite people. Each person you invite gets an email, chooses a password and goes through their own onboarding.
Access is controlled by roles. Under Access, open Roles to start from Role templates, build your own with Create role, or compare two roles side by side. Sign-in & security holds your sign-in rules and single sign-on, and Governance holds the audit log. The sidebar shows only what your roles let you use. Show advanced reveals the more specialized pages.
6. Give a service its own API key
Automation shouldn’t run on a person’s credentials. In Directory, go to Service accounts and choose Create service account. Give it a name, optionally a description and an inactivity deadline, and the roles it needs.
Open the account and choose Issue key. Give the key a label and a note on what it’s for, then pick an expiry from one day to one year (the default is 90 days). You can also limit the key to specific actions. The key is shown once, so copy it before you close the dialog. You can rotate it later from the same page, and API keys lists every key in the organization for review.
7. Add your SSH keys
Under Security & access, SSH keys holds the public keys your organization’s GPU instances accept. Members add their own keys, and every instance trusts every key on the list. That makes the list a complete answer to the question of who can sign in to your machines.
8. Plan, billing and support access
Plan & limits, in the Organization section of the IAM dashboard, shows the plan assigned to your organization, your usage against its limits and the products it includes. Administrators can request an upgrade from there. In the console, Billing & Cost holds your plan, the cost explorer, budgets, invoices and the rate card.
Also in the Organization section, LegionEdge support controls how far our support staff may act inside your organization: Off, Read-only or Troubleshoot. It lists live support sessions, which you can end, and keeps a history of what support did. If the page says support access isn’t set up, LegionEdge staff can’t open a session in your organization at all. Contact us if you want our support team to be able to help from inside it. See Identity & Access and Billing & Cost for more on each product.
