Creating an organization
When you sign in to app.guild.ai for the first time, Guild creates a personal organization for you automatically. To create a shared organization for your team:- Click your profile menu at the bottom of the left sidebar
- Select New organization
- Give it a name and invite team members
Organization settings
The standalone Organization settings section is not part of the settings sidebar. Navigating to/settings/organization or /organizations/{name}/settings/organization redirects to the Profile settings page. The organization identifier is displayed in the Profile Identity card under Profile settings. See Settings for details.
Members and roles
Organization members can access all workspaces within the organization. Invite members from Settings > Members in your organization. Admins can connect and disconnect credentials for organization-owned integrations. Members can use connected integrations but cannot manage their credentials.Pending invitation limits
Each recipient can hold at most 10 pending invitations at a time, counted across all organizations. When a recipient already has 10 pending invitations, Guild refuses any further invitation to them and the invitation fails with the message: “This recipient already has the maximum number of pending invitations. They have to accept or decline some before they can be invited again.” The recipient must accept or decline some pending invitations before you can invite them again. Pending invitations expire 7 days after they are sent. Expired invitations drop out of the recipient’s active invitation list and no longer count against the limit, so invitation slots free up automatically as old invitations age out.Accepting an invitation
Guild emails each invited person a verification code. Enter the code to confirm you control the email address and join the organization. If you are already signed in to Guild and your account email matches the invitation email address, you can accept the invitation with a single click. Guild compares the two addresses case-insensitively, so capitalization does not matter. You do not need to enter a verification code, because a matching account email already proves you control the invited inbox.App-wide invitation prompt
After you sign in and finish onboarding, Guild surfaces any pending organization invitations in an app-wide prompt. Accept or decline each invitation directly from the prompt. If you dismiss the prompt, Guild remembers that choice for the rest of the browser session.Locked-organization gate
If you open an organization’s URL (for example,/organizations/team-name) while your invitation to that organization is still pending, Guild withholds the organization’s content and shows it as locked. Click View invitation to review the invitation, then accept it to unlock the organization in place. If you decline, Guild redirects you to the homepage.
Organization profile
The organization profile includes the organization name, bio, avatar, and social links. Access it from Settings > Profile in your organization.Only Admin users can edit the organization profile.
Insights
The Insights section gives organization admins visibility into activity and resource consumption.Audit logs
Audit logs record every attempt to change something through the Guild API in your organization — successful or not. A refused attempt is recorded alongside its status code, so a denied action still leaves a trace. Rejected requests are logged without their request body. Read-only requests are not logged, and neither are internal runtime and operator traffic. Go to Insights > Audit Logs to view the log.Only Admin users can view audit logs.
Usage
Usage shows organization-level metrics and quota consumption. Go to Insights > Usage to view them.Credentials
Service credentials (GitHub, Slack, Jira, etc.) are configured at the organization level. When an agent needs access to a service, it uses the credentials connected to the organization. Go to Settings > Credentials to connect services. See Credentials for details.LLM settings
Configure how Guild runs LLM calls for the organization in Settings > LLM Settings. Organization admins can use managed Guild tokens or add provider API keys (BYOK) for workspaces owned by the organization. See LLM settings for details.Danger zone
Organization admins can request permanent deletion of the organization from Settings > Danger Zone. Submitting the request notifies Guild support, who processes the deletion manually.Next steps
Workspaces
Create workspaces within your organization.
Credentials
Connect third-party services.
LLM settings
Configure managed LLM access or provider API keys.