Skip to content
CCS Chat Docs

Standalone Chat in 10 minutes

In standalone use, people chat at chat.centralcodestation.com with their Identity Server account and you write no code. You will sign in as the workspace owner, give a role permission to use Chat, and check that a colleague can chat. This page is for the owner or admin of a workspace (your tenant).

What you need

Section titled “What you need”
  • You are the tenant_owner of the workspace, or you hold administration.manage.
  • At least one application of the workspace has Chat enabled. Every application has it unless it was switched off. See Switch Chat on for an application.
  • The people who will chat have accounts in the workspace and hold a role, for example tenant_user.

Set it up

Section titled “Set it up”

  1. Sign in. Go to chat.centralcodestation.com, select Sign in, then Continue with Central Code Station. Use your Identity Server account.

  2. Choose a workspace and an application. On Choose a workspace, select your workspace (your tenant). On Choose where to chat., select an application. If you have only one of each, Chat skips these screens.

  3. Open Chat Administration. Select Administration in the top bar. If you do not see it, you are not the owner and your role has no administration permission yet.

  4. Let your admins administer. Open Roles & permissions. In Where, keep Tenant-wide (administration). For the tenant_admin role, tick administration.read and administration.manage and select Save. Each checkbox is labelled with a description; hover over it to see the permission key. Only the owner can do this at first: every role except tenant_owner starts with no Chat permissions.

  5. Let people chat. In Where, choose Chat inside your application. For the role your people hold, such as tenant_user, tick the permissions in the table below and select Save.

  6. Tell people to sign in. They go to chat.centralcodestation.com, sign in the same way and pick the workspace and application. Permissions apply within about a minute of saving.

Permission What it lets people do
conversations.read See their conversations
messages.read Read messages, react, and mark them read
messages.send Write messages and replies
users.lookup Search for colleagues in Search people (2+ letters)…
conversations.create Start conversations with + Conversation

Add groups.create for groups and channels.create for channels. See Permission sets for standalone use for ready-made sets.

Verify

Section titled “Verify”
  1. Ask a colleague whose role you just set up to sign in and choose the application.
  2. They see + Conversation. They search for you, select your name and select Start conversation.
  3. You see the conversation appear in your list with a New label. Open it and reply.

If the colleague sees “Your role (…) doesn’t allow any Chat actions in this workspace yet”, the role has no Chat permissions in that application. If they see “you don’t have a Chat role yet”, they hold no role in the workspace: assign one in the Identity Server.

What a person with no permissions can do

Section titled “What a person with no permissions can do”

A person who holds only tenant_user, with nothing granted to that role in Chat, can sign in and open Chat but nothing more. They cannot look up other people or start conversations, and Chat tells them to ask their tenant admin. A tenant_user does not get Chat permissions automatically.

To let them take part in conversations that someone else creates, for example conversations your backend opens in an integrated setup, grant conversations.read, messages.read and messages.send, and leave out users.lookup and conversations.create.

Next steps

Section titled “Next steps”