Accounts, organizations, and security
Every protected ForgeLore session has an active organization. Switching organizations immediately changes which repositories, members, usage, and AI assistants you can access.
Use the account and organization menus in ForgeLore to manage profile security, sessions, invitations, and roles.
Manage your account
Update profile information, email identities, connected accounts, MFA, and active sessions from the account menu.
Choose your team
Personal workspaces are hidden. Select or create an organization before entering protected ForgeLore routes.
Role-based access
Organization roles and permissions control billing, members, repositories, locks, and AI assistant administration.
Server-enforced scope
Changing a URL or request organization ID cannot override the organization in your authenticated session.
Before you begin
Sign in with a verified account. To create an organization, you must be allowed to create team workspaces. To change members, roles, security, or billing, use an organization administrator account.
Create and switch organizations
- Open the organization switcher in ForgeLore navigation.
- Select an existing team or choose the creation flow.
- After creation, ForgeLore synchronizes product state and activates the organization.
- Switching teams updates repositories, usage, members, billing, and assistant access together.
Account and product settings
Secure account pages manage profile details, email identities, connected accounts, multi-factor authentication, sessions, organization name and logo, memberships, invitations, verified domains, enterprise connections, and security settings.
ForgeLore organization pages add product defaults, notifications, repository and assistant summaries, billing, usage, budgets, alerts, and invoices.
Access problems
If ForgeLore asks you to choose an organization, complete that task instead of editing the URL. If a page is forbidden, ask an organization administrator to review your role. If a newly created organization does not appear immediately, refresh once and retry the organization selection flow.
Verify access
After switching organizations, confirm that the organization name in navigation matches the team you intended to open. Check that repository, usage, and member lists belong to that organization before making changes.