# Workspace owner and admin (/docs/roles/organization-owner-and-admin)

A workspace has its own roles, separate from the factory roles on [Roles at a glance](/docs/roles).
They decide who may manage the workspace itself: its name, its members and its invitations.

| Workspace role | Who | What it is for |
|---|---|---|
| **Owner** | The person the workspace was created for | Everything, including renaming the workspace and managing every member. There is always one. |
| **Admin** | Someone the owner trusts to run it | Manage members and invitations. |
| **Member** | Everyone else | Work in the workspace. No member or invitation management. |

The **Org admin** is a different thing. It is a Factory OS app role: full access to every module and
the only role that edits roles and permissions, standards and operating hours. See
[Org admin](/docs/roles/org-admin). A person can be a workspace member and the Org admin, or a
workspace admin and a Planner.

## Where you start [#start]

You manage members and invitations in two places. Both are open to the workspace owner.

- **Organizations** in the main navigation lists your workspaces, their members and invitations.
- **Settings > Users & invitations** inside Factory OS invites people with a Factory OS role.

<GuideStep
  title="Organizations"
  description="Your workspaces, with the members and invitations of the one that is active."
  src="/guide/roles-organization-owner-and-admin/1.png"
  alt="Organizations page on desktop with the workspace list, members and invitations"
  width={1440}
  height={1000}
  callouts={[
    { x: 30, y: 22, caption: "Switch or create a workspace." },
    { x: 50, y: 42, caption: "Members of the active workspace and their workspace role." },
    { x: 70, y: 60, caption: "Pending invitations. Resend or revoke them here." },
  ]}
/>

<GuideStep
  title="The launcher as the workspace owner"
  description="The apps launcher shows every module your Factory OS role can open."
  src="/guide/roles-organization-owner-and-admin/2.png"
  alt="Apps launcher on desktop showing every module for the Org admin"
  width={1440}
  height={1000}
  callouts={[
    { x: 18, y: 24, caption: "My work: records waiting on you." },
    { x: 82, y: 24, caption: "Settings: members, roles and permissions, organization settings." },
  ]}
/>

<GuideStep
  title="Your queue on a phone"
  description="My work on a phone."
  src="/guide/roles-organization-owner-and-admin/3.png"
  alt="My work queue on mobile for the Org admin"
  width={375}
  height={812}
  callouts={[
    { x: 50, y: 6, caption: "Page title and your role." },
    { x: 50, y: 30, caption: "One card per record waiting." },
  ]}
/>

## What you can do [#can]

- **Invite people** with a Factory OS role, and revoke or resend an invitation. See
  [Invite your team](/docs/organizations/invite-members).
- **Change or remove a member.** Change their workspace role, or remove them. Removing a person
  ends their access on their next request.
- **Rename the workspace** or change its details. Only the owner may do all of this; an admin may
  only do it when their Factory OS role has full Settings access.
- **Transfer ownership** to another member.

## What you can see but not change [#view]

A workspace admin whose Factory OS role has Settings on **View** can read the settings and cannot
change them.

## What you cannot do and who does it [#cannot]

These checks run on the server, whatever the screen shows.

| You try to | Message | Who can do it |
|---|---|---|
| Change workspace settings without being the owner or having full Settings access | `Only the organization owner or a member with full Settings access can do this.` | The owner, or a member whose role has full Settings access. |
| Change them when your role has Settings on View | `Your role can view Settings but not change it.` | The Org admin changes your access. |
| Change the organization details when you are not the Org admin | `Only the Org admin can change the organization details.` | The Org admin. |
| Act after your factory access window ended | `Your access to the factory system has expired. Ask your administrator to renew it.` | An administrator renews it under **Settings > Entities & access**. |

## A typical day [#day]

<Steps>
<Step>

Open **Organizations** and check the invitations that have not been accepted. Resend any that
expired after 7 days. Details: [Invite your team](/docs/organizations/invite-members).

</Step>
<Step>

When a person joins or changes job, set their Factory OS role. Details:
[Users and invitations](/docs/settings/users-and-invitations).

</Step>
<Step>

When someone leaves, remove them. Details: [Workspaces](/docs/organizations/create-and-switch).

</Step>
</Steps>

<NextSteps>

<NextStep href="/docs/organizations/invite-members" title="Invite your team" description="Invite people with a Factory OS role." />

<NextStep href="/docs/roles/org-admin" title="Org admin" description="The app role that edits roles, standards and hours." />

<NextStep href="/docs/roles" title="Roles at a glance" description="Compare the factory roles." />

</NextSteps>