# Link your Roblox account and your Open Cloud key

> Public channel — documentation of app 3.6.3. Follow the availability notices of each service.

Source: [Link your Roblox account and your Open Cloud key](/en/application/studio/compte-roblox/)

The linked account belongs to each person. The Open Cloud key belongs to the project owner.

VibeStarter needs two different Roblox credentials, and mixing them up is the most common cause of getting stuck. The **linked Roblox account** publishes assets. The **Open Cloud key** creates Game Passes and developer products. One does not replace the other.

## Which one do you need?

| What you want to do | What you need |
| --- | --- |
| Publish images, sounds, 3D models, animations | **Your linked Roblox account** — no key |
| Create **Game Passes** and **developer products** | **An Open Cloud API key** pasted into the app |

What VibeStarter does not do

VibeStarter never touches your Robux. The Open Cloud key is used only to create the Game Passes and developer products of your game.

## Link your Roblox account

1.  Open Settings → Roblox account, in the Connections group.
2.  Click Connect Roblox. The app opens Roblox in your browser.
3.  Authorize the app on the Roblox page, then go back to VibeStarter.
4.  The app shows Connected as followed by your account. Your agents can now publish your creations to Roblox.

You can also do this during setup, at the step “Connect your accounts” (“Optional: you can do it later in Settings.”), on the Roblox card: “Publish your 3D models, sounds and images straight to Roblox.”

## What Roblox shows on the consent screen

When you click Connect Roblox, Roblox opens the “Your Accounts” page. It lists the two permissions requested, **Write Assets** and **Read Assets**, then the accounts you can grant them to: your personal account, and **only the groups you own**. A group where you are a member, even with the right to edit its experiences, does not appear in this list. Roblox does not let a member authorize uploads on behalf of the group.

Select every account or group that owns a game you are going to work on. A group you forget at this step shows up later as a permission refusal on the first upload.

To add a group later, click Refresh permissions on the card of the linked account. The app disconnects the account and reopens this page, where you select the group.

Your Roblox tokens do not go through the app

VibeStarter does not call Roblox from your computer. The permissions are held and renewed by its servers. No Roblox token passes through the interface.

## Which account does a published asset end up on?

**The owner of the game in your project decides.** VibeStarter reads it from the linked place, opened in Studio, and keeps it for the project. The asset goes to **the account or group that owns this game**, even if Studio is closed once this owner is known.

Until the owner is known — place never linked, never published, or Studio closed before any reading — the asset still goes out, to **your personal account**. Only one case blocks publishing: the open place belongs to another project.

When the asset goes to your personal account this way, the app warns you: “VibeStarter couldn’t confirm this project’s Roblox owner (Studio closed or in a playtest), so the upload went to your personal account instead of the group. Link the place to route uploads to the right owner.” The

Link the place button is offered right next to it.

### Personal account or group?

Both work. A game owned by a group makes invitations and revenue sharing easier. In both cases, you must be **the owner of the experience or, for a group experience, the owner of the group**. A group can own several experiences: its owner authorizes VibeStarter once, for all of them. The only exception is teamwork, where the project owner can let collaborators publish in their name. See [Working with others on a project](/en/application/projet/equipe/). For your assets to go to the group, the open place must belong to that group and be linked to your project.

## Create your Open Cloud API key

The app guides you: Settings → Keys & generation → the

How to create your Roblox API key assistant, in five steps on Roblox’s Creator Hub. The settings to respect:

| Setting | Expected value | Why |
| --- | --- | --- |
| `Game Passes` permission | read **and** write | create and edit Game Passes |
| `Developer Products` permission | read **and** write | create and edit developer products |
| `Restrict by Experience` | off | one key covers all your games |
| IP address restriction | off | the key is used from VibeStarter’s servers, not your machine |
| Expiration | `No Expiration` | avoid an outage after a few weeks |

Then paste the key into the app and use Test the key. The test gives a verdict for each permission: `verified`, `denied`, or `not verified`. If the key is restricted by IP address, the app says so clearly: “Restricted by IP — this will block VibeStarter.”

A Roblox key expires after 60 days of inactivity

The app itself shows this warning: a Roblox API key expires after 60 days of inactivity, **even with `No Expiration`**. If your monetization stops working after several weeks without use, create a new key and paste it again.

## Reuse an asset that is already published

Each published asset keeps the link between its Roblox ID and its source. Your agents can therefore reuse an asset that is already online without starting again from the original file, including from another computer connected to the same account, or for a member of the same project team.

However, your local library does not sync from one machine to another. See [Where your assets go](/en/application/assets/ou-vont-tes-assets/).

## Limits

-   The Open Cloud key belongs to the project owner: it is not shared with the team.
-   The Open Cloud key is saved on the computer, not in your VibeStarter account: it stays usable by the next account that signs in on it. The app flags this at sign-in; on a shared computer, remove your key in Settings → Keys & generation before you leave the place.
-   Without a linked Roblox account, your agents cannot publish anything to Roblox.
-   As long as the game owner has not been read from the linked place, an asset goes to your personal account, with a warning.

## Frequently asked questions

**Is the linked account enough for Game Passes?** No. Game Passes and developer products require the Open Cloud key, in addition to the linked account.

**My asset went to my personal account instead of the group.** The place could not be read at the time of sending: Studio was closed, in a playtest, or the place was never published. Link the place, open it in Studio, publish it at least once, then try again.

**Roblox refuses my uploads for lack of permission, even though I have rights in the group.** The right to edit the group’s experiences is not enough: Roblox only offers a group on the consent screen to its owner. If you are not the owner, the owner is the one who links their Roblox account, invites you to the VibeStarter project, and checks Let the team publish in my name; the full order is in [Working with others on a project](/en/application/projet/equipe/#when-the-game-belongs-to-a-roblox-group). If you are the owner and the group was not selected at sign-in, use the Refresh permissions button and select it.

**I get an authorization error on monetization.** A permission is missing on the key. Add `Game Passes` and `Developer Products` with read and write access, then run Test the key again.

**What does VibeStarter see of my Roblox account?** The permissions requested cover your profile and asset publishing. Nothing that touches your Robux.

**Can my teammates see my Roblox account?** Each team member can see the Roblox account they linked in the team panel. If they have not linked one, nothing is shown. See [Working with others on a project](/en/application/projet/equipe/).

## Go further

-   [Your API keys and your credential store](/en/application/reglages/cles-et-trousseau/)
-   [Link a place to your project](/en/application/studio/lier-une-place/)
-   [Where your assets go](/en/application/assets/ou-vont-tes-assets/)
-   [Publish your game and track your versions](/en/application/studio/publier/)