Admin Guide

This guide covers everything an Owner or Admin needs to configure for their team — social media connections, Atlassian integration, API keys, project Atlassian mappings, and user management.

Organization Settings

Organization Settings are accessible from the left sidebar → Settings → Organization. This is the central location for all team-wide configuration.

General settings

• Organization name — The internal name used across the app.
• Display name — Shown on your public roadmap and in emails sent to survey respondents.
• Description — A short description of your organization, shown on public-facing pages.

Save changes by clicking Update Organization.

Connecting Social Media

Social media connections are set at the organization level and shared across all projects. Connected accounts can be used by any team member with Member role or above to publish and schedule posts.

Go to Settings → Social Media to manage connections.

LinkedIn

1. Click Connect LinkedIn.
2. You are redirected to LinkedIn to authorize Release Cadence. Sign in with the account you want to post from.
3. Grant the requested permissions (post on your behalf).
4. You are redirected back to Release Cadence. The account appears as connected with a green status badge.

LinkedIn tokens expire periodically. When they do, the connection shows as Expired. Click Reconnect and repeat the OAuth flow to restore access.

Slack

1. Click Connect Slack.
2. Select the Slack workspace to connect.
3. Choose the default channel for Release Cadence posts (this can be overridden per-post).
4. Click Allow. The workspace appears as connected.

Discord

1. Click Connect Discord.
2. Authorize Release Cadence to post to your Discord server.
3. Select the server and default channel.
4. Click Authorize. The server appears as connected.

For a full guide on creating and scheduling social media posts, see Social Media documentation.

Connecting Atlassian

The Atlassian connection is established once at the organization level using OAuth. Once connected, any project can be mapped to specific Jira projects, JPD boards, and Confluence spaces.

Step 1 — Connect your Atlassian instance

1. Go to Settings → Atlassian.
2. Click Connect Atlassian.
3. You are redirected to Atlassian's OAuth consent screen. Sign in with an account that has admin access.
4. Review and accept the requested permissions.
5. You are redirected back to Release Cadence. Your Atlassian instance appears as connected.

Step 2 — Map a project to Atlassian targets

Each project is independently mapped to Jira, JPD, and Confluence. Mapping is done from the project's own settings, not from Organization Settings.

1. Open the project you want to configure.
2. Go to Project Settings → Atlassian.
3. Select a Jira project — features pushed as Epics and requirements pushed as Stories will go here.
4. Select a JPD board (optional) — features and surveys pushed to JPD will appear here.
5. Select a Confluence space and parent page (optional) — design documents pushed to Confluence will be created under this parent.
6. Save. Team members on this project can now push to these targets.

Token refresh

Release Cadence automatically refreshes Atlassian tokens in the background — you don't need to take any action under normal operation. If the connection does show as Expired or Error, it means the underlying refresh token was invalidated. This typically happens if someone revokes Release Cadence's access from Atlassian's connected-apps settings, or if the integration hasn't been used for an extended period. In that case, click Reconnect and repeat the OAuth flow. All project mappings are preserved — you only need to re-authorize, not re-map.

API Key Management

API keys are used by the Atlassian Forge app to authenticate with Release Cadence. You need to generate an API key when setting up the Forge app in Confluence or Jira.

Go to Settings → API Keys.

Generate a key

1. Click Generate API Key.
2. Give the key a descriptive label (e.g., "Forge App - Production").
3. Click Generate.
4. Copy the key immediately. It is shown in full only once.

Rotate a key

To rotate a key (for example, after a suspected compromise):

1. Generate a new key.
2. Update the Forge app configuration in Confluence or Jira with the new key.
3. Confirm the Forge app is working with the new key.
4. Delete the old key from the API Keys list.

Revoke a key

Click Delete next to any key to revoke it immediately. Any service using the revoked key will stop receiving data from Release Cadence until it is updated with a valid key.

Managing Users

Go to Settings → Members to manage who belongs to your organization and what role they have.

Inviting team members

1. Click Invite Member.
2. Enter the person's email address.
3. Select their organization role:
   • Admin — Can manage settings, connections, and members. Cannot transfer ownership.
   • Member — Can access projects they are added to. Cannot change organization settings.
   • Viewer — Read-only access to projects they are added to.
4. Click Send Invitation. The invitee receives an email with a link to accept.

Pending invitations are listed in the Members table. You can cancel a pending invitation at any time.

Changing a member's role

1. Find the member in the Members table.
2. Click the role dropdown next to their name.
3. Select the new role. The change takes effect immediately.

Removing a member

1. Find the member in the Members table.
2. Click Remove.
3. Confirm. The member loses access to all projects in the organization immediately.

See Team Management for a full breakdown of roles and permissions.

Plan and Billing

Only the Organization Owner can manage billing. Go to Settings → Billing to:

• View your current plan and usage (projects, team members, storage)
• Upgrade to Pro
• Access the Stripe customer portal to update payment method, view invoices, or cancel

Plan limits are enforced when creating new resources. If a team member hits a limit (e.g., maximum projects on Basic), they will see an upgrade prompt. As an Admin, you will also see usage warnings in Organization Settings when approaching limits.

Checklist: Setting Up a New Team

Use this checklist when onboarding a new organization:

1. Set organization name and display name in Settings → Organization
2. Connect social media accounts: LinkedIn, Slack, Discord in Settings → Social Media
3. Connect Atlassian via OAuth in Settings → Atlassian (Pro plan required)
4. Generate an API key in Settings → API Keys and configure the Atlassian Forge app — see Atlassian Integration
5. Invite team members in Settings → Members
6. Create your first project and add team members to it
7. Map the project to Atlassian targets in Project Settings → Atlassian