About RoSignal

Product and permissions overview · Last updated August 25, 2026

RoSignal is a creation and productivity tool for Roblox creators and studios. It gives a creator one place to manage the ongoing lifecycle of the experiences they own: changing live configuration values without shipping a new build, rolling a change out gradually, sending operational messages to running servers, moderating disruptive players, scheduling routine operational work, and automating those same operations on a trigger. Analytics exist inside RoSignal only as supporting context for those decisions — the product people pay attention to is the management and automation layer.

App category

RoSignal belongs in Creation & Productivity Tools: it is a digital service used for content creation and the management of an experience's lifecycle after publish. Its primary functions write operational state to a creator's own experiences. It is not primarily a data-analysis product, and it is not a marketing, monetization, or social product.

Permissions we request, and why

openid

Identifies the creator who is signing in, so RoSignal can create and secure their workspace.

Never used to look up accounts other than the signed-in creator.

profile

Reads the signed-in creator's username, display name, and avatar so the workspace and audit logs show who performed each action.

Never used to collect profile data about players or other users.

universe-messaging-service:publish

Publishes the creator's own operational updates — live configuration values, scheduled operational messages, and moderation commands — to the running servers of experiences the creator owns or is authorized to manage. This is the delivery channel that makes the tooling work without a code push and a full restart.

Never used to message experiences the signed-in creator does not own or manage, never used to read player data, and never used to deliver third-party or advertising content.

RoSignal requests no other scopes. We do not request restricted player data, we do not sell or share any data with third parties, and every authorized experience can be disconnected by the creator at any time.

How it works

1. Sign in with Roblox

The creator authorizes RoSignal with Roblox OAuth 2.0 and selects which of their experiences to grant access to. Nothing happens until the creator explicitly picks an experience.

2. Install the open listener module

The creator adds a small, readable Luau script to their experience. It subscribes to a single MessagingService topic and applies whatever the creator publishes from their own dashboard.

3. Manage the experience over its lifecycle

From the dashboard the creator changes live config values, rolls a value out to a percentage of servers, schedules an operational message, or issues a moderation action — all against their own experience, all recorded in an audit log.

local MessagingService = game:GetService("MessagingService")
local RoSignal = require(script.Parent.RoSignal)

-- One topic, owned by this experience. Everything RoSignal
-- publishes arrives here and is applied by the creator's own code.
MessagingService:SubscribeAsync(RoSignal.Topic, function(message)
	RoSignal.Apply(message.Data)
end)

The listener is visible to the creator, runs in their experience, and only applies payloads published by their own workspace. Nothing is executed as arbitrary code.

Safety, access control, and data handling

Owner authorization. A creator can only act on experiences returned by their own Roblox authorization.
Role-based team access. Owner, Admin, Developer, and Viewer roles limit who can publish changes to a live experience.
Audit logs. Every config change, message, and moderation action records who performed it and when.
Rate limits and cooldowns. Automations enforce cooldowns, hourly run caps, and loop protection, and can be dry-run before going live.
Data stored. Roblox account identifiers, encrypted OAuth tokens, the experiences a creator authorizes, and the configuration, schedules, and logs the creator creates. Deleting a workspace deletes this data.

Full details are in our Privacy Policy and Terms of Service.

Contact

For review questions or support, reach us on Discord at thunder_thigh or in the RoSignal Discord server. The product itself lives at rosignal.app.