# Team Permissions

Game Launcher Cloud uses a role-based permission system to control what team members can do with shared apps, launchers, and news.

***

## Permission Levels

### Owner (Level 5)

**Full Control** - Complete access to everything

* ✅ Create, edit, delete all content
* ✅ Manage team members
* ✅ Modify billing and subscriptions
* ✅ Delete apps, launchers, and news
* ✅ Configure all settings
* ✅ Access sensitive data

### Admin (Level 4)

**Administrative Access** - Manage content and team

* ✅ Create, edit, delete content
* ✅ Invite and remove team members
* ✅ Upload builds
* ✅ Deploy launchers
* ✅ Publish news
* ❌ Cannot delete apps or launchers
* ❌ Cannot modify billing

### Editor (Level 3)

**Content Management** - Edit existing content

* ✅ Edit apps, launchers, and news
* ✅ Upload images
* ✅ Modify settings
* ❌ Cannot delete content
* ❌ Cannot upload builds
* ❌ Cannot deploy launchers
* ❌ Cannot manage team

### Developer (Level 2)

**Build Access** - Upload and manage builds

* ✅ Upload game builds
* ✅ Edit build configurations
* ✅ View analytics
* ❌ Cannot modify app settings
* ❌ Cannot delete content
* ❌ Cannot deploy launchers

### Viewer (Level 1)

**Read-Only Access** - View content only

* ✅ View apps, launchers, and news
* ✅ View analytics dashboards
* ❌ Cannot modify anything
* ❌ Cannot upload content

***

## Permission Matrix

| Action           | Viewer | Developer | Editor | Admin | Owner |
| ---------------- | ------ | --------- | ------ | ----- | ----- |
| View Content     | ✅      | ✅         | ✅      | ✅     | ✅     |
| Upload Builds    | ❌      | ✅         | ❌      | ✅     | ✅     |
| Edit Settings    | ❌      | ❌         | ✅      | ✅     | ✅     |
| Upload Images    | ❌      | ❌         | ✅      | ✅     | ✅     |
| Publish News     | ❌      | ❌         | ✅      | ✅     | ✅     |
| Deploy Launchers | ❌      | ❌         | ❌      | ✅     | ✅     |
| Delete Content   | ❌      | ❌         | ❌      | ❌     | ✅     |
| Manage Team      | ❌      | ❌         | ❌      | ✅     | ✅     |
| Manage Billing   | ❌      | ❌         | ❌      | ❌     | ✅     |

***

## How Permissions Work

### UI Elements

The interface automatically adjusts based on your permissions:

* **Disabled Buttons** - Actions you cannot perform are grayed out
* **Hidden Options** - Some features are hidden if you lack access
* **Permission Alerts** - Clear messages explain why actions are blocked

### Demo Content

{% hint style="warning" %}
**Special Rule:** Demo content can only be modified by platform owners, regardless of your role in other content.
{% endhint %}

### Developer Role Requirement

Many actions require **Developer role (Level 2) or higher**:

* Uploading app builds
* Modifying launcher configurations
* Deploying environment changes
* Publishing news articles

***

## User Storage Management

### Storage Breakdown

View detailed storage usage by category:

* **Apps** - Game build storage
* **Launchers** - Launcher build storage
* **News** - News images and media
* **Profile** - Profile images and assets

**Accessing Storage Breakdown:**

1. Navigate to **Dashboard → Overview**
2. Locate the storage card
3. Click **View Breakdown** to expand details

### Storage Limits

Each plan includes specific storage limits:

* Real-time usage tracking
* Notifications when approaching limits
* Automatic reset each billing cycle

{% hint style="info" %}
**View Limits:** See your storage quota and usage in **Dashboard → Overview → Storage**
{% endhint %}

### Build Limit Exceeded

When you reach your build upload limit:

* Further uploads are blocked
* Email notification sent
* Clear error message with usage details
* Countdown shows when limits reset

**Resolution Options:**

1. **Wait for Reset** - Limits reset at the end of your billing cycle
2. **Upgrade Plan** - Increase your limits immediately
3. **Delete Old Builds** - Free up space by removing outdated builds

***

## Admin Features

### User Storage Inspection

Admins can view storage breakdown for any user:

* Detailed category breakdown
* Usage trends and patterns
* Delete content with optional reason

### Delete Confirmation

When deleting user content, admins must:

1. Confirm the action
2. Optionally provide a reason
3. Action is logged for audit trail

***

## Best Practices

**✅ Assign Minimum Permissions**

Give team members only the access they need

**✅ Use Developer Role for Build Access**

Separate build upload permissions from content editing

**✅ Regular Audits**

Review team permissions periodically

**✅ Owner Role Limitation**

Minimize the number of users with Owner access

**✅ Monitor Storage**

Keep track of storage usage to avoid hitting limits

***

## Frequently Asked Questions

**Q: Can I have multiple Owners?**\
A: Yes, but it's recommended to limit Owner roles for security. Owners have full access including billing.

**Q: What happens if I exceed storage limits?**\
A: You'll receive notifications and won't be able to upload new builds until you free up space or upgrade your plan.

**Q: Can Developers deploy launchers?**\
A: No, only Admin and Owner roles can deploy launchers to ensure controlled releases.

**Q: Why can't I edit demo content?**\
A: Demo content is managed by the platform to ensure consistent quality for all users exploring the system.

**Q: How do I change a team member's role?**\
A: Navigate to **Team Settings**, find the member, and select their new role. Only Admins and Owners can change roles.

***

{% hint style="info" %}
**Need Help?** Contact us at <support@gamelauncher.cloud> or join our [Discord](https://discord.com/invite/FpWvUQ2CJP)
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://gamelauncher.cloud/help/help-center/permissions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
