Workspaces and teammates

A workspace is the Lore home for one GitHub organization or personal account. It has its own connected repositories, members, subscription, and shared monthly read allowance. Switching workspaces does not combine their quotas or bills.

Create another workspace

Open the workspace selector and choose + New workspace. Continue to GitHub, choose the organization or personal account, and install Lore on the repositories you want to connect. An organization owner may need to approve the installation. Return to Lore and refresh your GitHub connection if the workspace has not appeared.

For example, connecting acme and your personal GitHub account produces two workspaces. Installing Lore on acme again connects you to its existing workspace. It does not create a duplicate or give it another Free allowance.

Lore starts ingesting automatically. There are no facts to approve before your agent can use the available context.

Invite a teammate

An administrator opens Settings → Members → Invite member, enters the person's GitHub username, and chooses a role. Free includes one seat, so upgrade before inviting teammates.

After creating the invitation, copy the sign-in link and send it to that person. Lore does not send an invitation email. They accept by signing in with the matching GitHub account, which must have access to the connected GitHub installation.

An invitation does not grant repository permissions. If Maya can access acme/website but not acme/payments, inviting Maya to Lore still does not let her read the payments repository's memory.

Pending invitations do not count as paid seats. Accepted, active teammates do. Regular teammates need an invitation; GitHub account owners and organization administrators can establish their workspace when they sign in.

Choose roles

• Member: uses Lore with their authorized repositories and sees shared usage.
• Administrator: also manages workspace settings, members, policy, and billing.

A role deliberately assigned in Lore stays in place when the person signs in again. Repository access still follows GitHub, regardless of their Lore role.

Hand over administration

Promote an active teammate to Administrator in Settings → Members. You can then change your own role or have them remove your access. A pending invitation does not count: the teammate must have accepted and still have GitHub access. Lore prevents these changes from removing the last active administrator.

This hands over administration inside Lore. It does not transfer ownership of the GitHub organization or personal account.

Remove or restore access

Use Remove access for an active member, or Cancel invitation for someone who has not joined. Removing a member blocks future access to this workspace; it does not sign them out of their other workspaces.

Restore access does not grant GitHub permissions. If their GitHub access was removed, restore it in GitHub too. Paid seat counts follow accepted, active members.

Rename a workspace

Open Settings → Workspace, edit the display name, and save. This only changes the name in Lore, not the GitHub account name, repositories, plan, or subscription.