Skip to content

Settings and roles

Open the Rudder Dashboard and enter your email: a link comes to it, and opening the link creates the account and signs you in. It works once and expires in 24 hours. An account that exists already gets a link that expires in 15 minutes. A link can be asked for again from the sign-in page.

You may also sign up with an email and a password. Such an account waits for the link we send to it, and works after that link is open.

A password that is forgotten is reset from the sign-in page: Forgot your password? sends a link that sets a new one. The link works once and expires in 15 minutes, and every session and personal access token of the account ends when the password changes. An account that still waits for approval gets no reset link — the link we sent at sign-up approves it.

Settings → Personal Access Tokens of your account (the account menu) creates a token for CI and your scripts. It is shown once and has the rights of your account in each of your projects. Signing in from the CLI creates one too, named cli <hostname>. Revoke any of them there.

Project Settings has four tabs:

TabWhat it contains
GeneralProject name and description, day start, plan and usage, and project deletion.
EnvironmentsSDK and server keys, and allowed origins for the environment selected in the header.
AuthenticationSign-in connections for the environment selected in the header.
MembersProject members and their roles.

General opens by default. The selected tab is saved in the address as ?tab=general, ?tab=environments, ?tab=authentication or ?tab=members, so reloading and browser Back and Forward keep your place.

The day start is a time in UTC at which days, weeks and months of the project start. It is part of the draft, so a change reaches players with the next release. Deleting the project removes everything in it and stops its keys at once.

In Environments and Authentication, choose Staging or Production in the header before opening a setting. Only the owner changes keys, origins and sign-in connections; these settings can be changed in Production too. Editors and support can view them.

See Sign-in providers to connect Google, Apple, Facebook, CrazyGames, Yandex, VK, an OpenID Connect provider or your own sign-in service.

KeyWhere it goesShown
SDK keyInto the game client. It selects the environment.Always.
Server keyInto the secrets of your game server only.Once, when it is issued.

Each environment, Staging and Production, has one of each. Issuing a new key stops the current one at once, so plan a new SDK key together with a client update.

A browser game, or a Unity WebGL build, calls Rudder from the page that hosts it. In Settings → Environments, Allowed origins lists the origins whose pages may call the selected environment, one per line; Save origins stores them. Only the owner changes them.

An origin is a scheme, a host and an optional port, such as https://play.example.com, at most 20 per environment. * allows any origin.

In Settings → Members, the owner adds a member by the email of an approved account, with a role:

OwnerEditorSupport
Members, keys, allowed origins, sign-in connections, the project itselfyes
Modules, catalogs, currenciesyesyesread
Publish, promote and roll backyesyes
Read playersyesyesyes
Function calls, balances, bans, profiles, unlinkingyesyes
Delete and restore playersyesyes

Removing a member or changing its role reaches player data within five minutes.