permission string
A server-enforced action grant such as
tickets.write, ranks.approve, or integrations.manage.product area
Rodyne’s first-party identity and controlled multi-community network system.
access model
Optional workspace access derived from the member’s current roles in the connected guild.
request identifier
A retry identity that prevents the same logical mutation from creating duplicate records.
configuration
A Roblox Group ID and Rank ID joined to a Discord role and Rodyne policy fields.
disclosure record
A reviewed, member-safe view of one eligible source record. It can be withdrawn without erasing its audit history.
Roblox group
The workspace group whose ladder powers normal promotion, demotion, and rank requests.
policy
A mapping that cannot be requested as a target and whose Discord role is not automatically changed.
verification
A follow-up query that confirms Discord or Roblox now holds the intended state.
Roblox group
A bound group used for Discord role synchronization but not ordinary rank requests.
job result
A provider write may have applied, but Rodyne could not safely prove the result. It requires live-state review before retry.
Roblox identifier
The stable experience identifier used to scope Studio connector credentials. It is different from a place ID.
tenant
A Rodyne community boundary with its own staff, provider resources, records, permissions, billing, and audit trail.
Guided walkthrough
Product terms map to visible workspace, identity, provider, and job concepts in the interface.
Operating procedure
1
Locate the noun
Identify whether the term describes a tenant, identity, configuration, record, or provider outcome.
2
Find its owner
Determine which workspace or network controls it.
3
Separate policy from state
A mapping or approval describes intent; provider read-back describes reality.
4
Follow references
Use the linked guide for procedures and the reference page for exact behavior.
5
Use precise language
Record uncertain, partial, and completed outcomes distinctly in staff notes.