> ## Documentation Index
> Fetch the complete documentation index at: https://academy.uagenius.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Workspace Administration

> Manage games, members, brand assets and the custom properties you tag files with.

The **Admin panel** holds the settings that shape how your whole team's console behaves: who has access, what the AI uses as visual references, and how your creative library is tagged.

<Note>
  Admin panel access comes with the admin role. If you do not see it in the navigation, an administrator on your team can grant it.
</Note>

## User management

Lists every member with their **Name**, **Email**, **Role**, **Games** and **Joined on** date.

**Invite users** takes comma-separated email addresses, a **Role**, and the **Games** the invitees should have access to, so you can bring several people into the same set of games in one action.

Access is granted per game, which lets you invite a contractor to one title while your other work stays private.

## Roles

Two roles are available:

| Role      | Access                                                                            |
| --------- | --------------------------------------------------------------------------------- |
| **admin** | Full access, including the admin panel.                                           |
| **user**  | The production surfaces: research, recreate, Video Studio, publishing and assets. |

Most of a team sits comfortably on **user**. Keep **admin** for the people who look after brand assets and membership, since those settings shape everyone's output.

## Games

Each game is listed with its **Name**, **Description**, **People**, **Created on** date, and two configuration entry points. **Create game** adds a new title.

<Tip>
  Work through [Set up your game](/setup) right after creating one. Uploading brand assets is the step that shapes every hook the team generates afterwards.
</Tip>

### Brand assets

**Brand assets → Edit brand assets** holds the images the AI uses as visual references when it builds a hook for you. It is per game, so each title keeps its own art.

See [Brand assets](/brand-assets) for what to upload, how to name it, and how the Recreate studio uses it.

### Custom properties

**Asset Properties → Manage** defines [the custom properties you can tag files with in Projects](/projects). Each field you create, with its own list of options, becomes a filter there under **Game space specific**.

These apply to the files in Projects. The filters in Competitor Research are separate, since those come with the market data rather than from you.

A typical set looks like:

| Field                     | Example options        |
| ------------------------- | ---------------------- |
| **Creative Concept**      | The angle the ad takes |
| **Style**                 | The visual treatment   |
| **Creative Concept copy** | The copy angle         |
| **Content style**         | The content format     |

These are yours to define, and the fields above are one game's choices rather than a fixed schema.

<Steps>
  <Step title="Decide what you will want to compare">
    Design the fields around the questions you will ask later: which concept performs best, which style wins on Android. Fields that feed a real comparison are the ones worth maintaining.
  </Step>

  <Step title="Keep option lists short">
    Three to six options per field keeps tagging consistent and filtering sharp.
  </Step>

  <Step title="Define them before generating at volume">
    Tagging as files are created takes seconds and keeps the library searchable from day one.
  </Step>
</Steps>

## Setting up a new game

<Steps>
  <Step title="Create the game">
    **Admin panel → Games → Create game**. Give it a clear name and description.
  </Step>

  <Step title="Define custom properties">
    So every file in Projects can be tagged as it arrives.
  </Step>

  <Step title="Upload brand assets">
    Characters, environments and key art, uniquely named.
  </Step>

  <Step title="Invite the team">
    Granting access to this game specifically.
  </Step>

  <Step title="Request body templates, if you need them">
    Only if the team wants to recreate gameplay. They can compose with competitor bodies or their own uploads without this. See [Request a body template](/request-body-template).
  </Step>
</Steps>