> ## Documentation Index > Fetch the complete documentation index at: https://docs.kinematic.run/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > These are the customer docs for kinematic, a name written in lowercase except at the start of a sentence. Kinematic provides provably fair casino games, served to a casino's site by a game server: a Cloudflare Worker that the kinematic dashboard deploys into the casino's own Cloudflare account. > Never put SESSION_SECRET or WALLET_SECRET in code, prompts, logs, commits or chat. Read them from environment variables and ask the person you work with to set them. The dashboard's Integration page shows each secret once. > Values such as lucky-star, luckystar.example, og-rgs-lucky-star.luckystar.workers.dev, games.luckystar.example and player_48213 are examples. Use the casino's own casino ID, game server origin, element tag, session issuer and currencies: the Instructions for your coding agent on the dashboard's Integration page hold them, or ask the person you work with. > To debug, start at https://docs.kinematic.run/troubleshooting and https://docs.kinematic.run/reference/errors. The wallet contract is at https://docs.kinematic.run/api/wallet.openapi.yaml. > Sandbox bets are recorded on Solana devnet. Live game servers record nothing on Solana until the audited mainnet program is deployed. # Team > Invite the people who work on your casino and choose what each one can change. Each casino has its own team. Everyone on it can see the casino; owners and admins change its settings, deploy and pay. Open **Team** to see the members, the pending invitations and what each role can do. ## Roles **Team** describes each role under `What each role can do`: | Role | What the page says | In practice | | - | - | - | | Owner | An owner does everything an admin does, and also changes roles and removes people. | The person who created the casino is its first owner. | | Admin | An admin changes settings, deploys the game server, pays and invites people. | Changes **Settings**, **Appearance** and **Games**, runs the first-run steps, deploys and updates game servers, stops and accepts new bets, reveals the secrets and runs **Check my wallet** on **Integration**, pays on **Billing**, and invites people and cancels invitations. | | Member | A member sees the casino, its bets and its billing, and changes nothing. | Opens every page, read only. | ## Invite someone Owners and admins see **Invite someone** at the top of **Team**. 1. Enter the person's **Email**, for example `dev@luckystar.example`. 2. Choose the **Role**: **Admin** or **Member**. **Member** is chosen by default. 3. Select **Send invitation**. The dashboard emails them a link that works for 7 days. You can also invite people during the first-run steps; see [Create your casino](https://docs.kinematic.run/dashboard/create-casino.md). The link opens the invitation page, `Join `. Someone without an account selects **Create an account** and signs up with the invited email; someone with an account selects **Sign in**. Once signed in, they select **Accept and open Lucky Star** to join and open the casino's **Home**, or **Decline**. The account must use the invited email and that email must be confirmed: signed in with another address, the page asks them to sign out and open the link again, and with an unconfirmed email it says `Confirm your email first, then open the invitation again.` ## Pending invitations While invitations wait, **Pending invitations** lists each one with its email, role, who invited them and the date its link works until. Owners and admins can select **Cancel** on a row and confirm with **Cancel the invitation**: the link stops working, and you can invite the person again later. ## Change roles and remove people In **Members**, owners change a person's role from the menu on their row; the change saves at once. This is also how you make someone an owner: invitations offer only **Admin** and **Member**. To take someone off the team, an owner selects **Remove** on their row and confirms. They lose access at once, and you can invite them again later. ## Leave a casino At the foot of **Team**, select **Leave Lucky Star** and confirm with **Leave**. You lose access until someone invites you again. The only owner cannot leave: the page says `You are the only owner. To leave , make someone else an owner first.` Make another member an owner in **Members**, then leave. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.