---
title: "RShift glossary"
description: "Key RShift terms, defined the way the product uses them."
image: "https://help.rshift.com/og.svg"
---

> Documentation Index
> Fetch the complete documentation index at: https://help.rshift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# RShift glossary

## Workspace and access

- **Workspace**: the shared container for brand context, people, AI credits, connected platforms, content, and settings. Everything in RShift is scoped to one workspace.
- **Member role**: what a person can do in a workspace. Owner, Admin, Editor, or Viewer.

## RShift AI

- **RShift AI**: the in-product AI workspace for generation, analysis, skills, and business tool calls.
- **Model collection**: the stable capability name RShift routes to, in the form `rshift-{capability}-models`. Capability codes are `tts`, `stt`, `trans`, and `privacy`.
- **Skill**: a reusable, on-demand workflow RShift applies when a matching task comes up.
- **Knowledge**: persistent workspace context RShift reads before it works.
- **AI credit**: the user-facing billing unit for AI usage. Credits are derived from real provider cost.

## Sites

- **RShift Sites**: the product entry point for complete websites and help centers.
- **Website**: a group of public pages with a shared identity and access point. Standard hosted websites use `handle.shift.fyi`.
- **Help Center**: a website for public help categories and articles. Standard hosted help centers use `handle.tidy.help`.
- **Page project**: a workspace-owned generated application with its own source and version history, independent of its eventual domain.
- **Project source**: the complete editable file tree of a generated application. It excludes dependencies, build output, runtime secrets, and live business data.
- **Project version**: a coherent point in a project source history, shared by all files changed in one accepted edit.
- **Publication**: a running release tied to a specific project version and backend environment.

## Content, channels, and publishing

- **Content item**: one piece of workspace content, with its variants, status, and history.
- **Channel**: a connected external platform account RShift can read from or act on.
- **Channel capability**: a normalized action or data surface a channel provides, such as publishing an article or reading followers.
- **Publication job**: a planned publishing task that decides what goes to which channel and when.
- **Publication delivery**: the channel-specific execution record for a publication job, storing provider ids, status, errors, and metadata.

## Growth and visibility

- **Search presence project**: a workspace-owned SEO and GEO target, owning the site origin, locales, keywords, competitors, prompts, schedule, and budget.
- **Search presence target**: one tracked keyword, competitor domain, or AI prompt.
- **Finding**: a deduplicated issue or opportunity derived from evidence, with severity, recommendation, and target URL.
- **Remediation**: converting an eligible finding into a revision-checked source change. It never publishes directly.
- **Attribution**: mapping recorded results back to the content, channel, and campaign that produced them.

## Automations and monitoring

- **Automation definition**: a workspace-owned task specification: trigger, schedule, prompt, skills, config, and status.
- **Automation run**: one execution, with its own snapshot, timeline, output, and terminal status.
- **Monitoring task**: a workspace-owned specification of what to watch, from which sources, in which regions, and how often.
- **Phone Agent**: the device app RShift uses for workflows that require a phone environment.

## Integrations and MCP

- **Integration**: an authorized connection to an external platform account.
- **MCP Gateway**: the single OAuth entry point that exposes RShift tools to your own AI clients.
- **RShift Connect**: the Chrome extension that lets RShift work with the page in front of you.

Source: https://help.rshift.com/glossary/overview/index.mdx