Workspace
What It Is
A workspace is the place where an association's records and daily work belong. It separates that work from other associations, including associations served by the same management company. The customer identifies the paying organization; the workspace identifies the operational space that organization administers.
Rhythm staff request a workspace through provisioning. They supply its readable identifier and configuration, and participating services prepare the records and resources needed to use it. The identifier remains its reference throughout its life and is reserved after deletion rather than assigned to a different workspace.
Two independent dimensions describe its standing. Business status expresses whether it is in implementation, live or disabled. Lifecycle state describes construction, loading, ordinary operation and retirement. Staff decide business status through the appropriate Rhythm HQ action; lifecycle work controls the operational state. A workspace can therefore be active in its lifecycle while still in implementation as a business decision.
What It Is Not
A workspace is separate from its paying customer and from the public site operated through Websites. Its configuration does not itself establish which applications are licensed. A sandbox is an additional workspace linked to a production parent; creating it does not copy the parent's association records.
How It Is Used
Staff follow provisioning progress, prepare an initial import and activate the workspace when that preparation is ready. A failed provisioning remains available for inspection and retry rather than disappearing with its partial work. Loading provides a controlled period for migration work while ordinary use is unavailable.
Rhythm HQ helps staff find workspaces by their identity and customer, return through personal shortcuts and inspect sender information. Customer administrators maintain the editable details within their authority. Retirement begins with disabling the workspace and making a recorded deletion request; staff can hold or cancel it before destruction starts.
Its Facets
Identifier and type. The readable reference identifies the workspace permanently. Customer, sandbox, demo, training and support types distinguish its purpose.
Sandbox relationship. A sandbox names a production parent under the same customer. It provides a separate place for preparation without establishing a copying workflow.
Business status and lifecycle. Commercial standing and operational readiness answer different questions. Loading, provisioning and deletion restrict ordinary use through the availability gate.
Details. Name, acronym and time zone support recognizable presentation and the calendar used for dated work.
Commercial link and sender. The commercial account supplies licensing information. A configured sender supports association-branded mail once verification is complete; provisioning does not wait for DNS publication.
Lifecycle requests. Provisioning, initial import, reset, activation and deletion provide accountable steps for bringing the workspace into use and retiring it.
Staff shortcuts. Pins and recent openings help each staff member return to their own working set.
How It Relates
A workspace belongs to one customer and can be the scope of ordinary or staff access. Portal members belong to its portal pool. Other applications retain their own association records within the workspace and participate in the lifecycle protocol when those records are created or removed.
What It Could Become
The product should settle access to disabled workspaces, enforce any required import-completion check before go-live, and provide appropriate deletion-request screens. Copying production data into sandboxes, customer-facing retirement notices and faster backup erasure remain distinct decisions. They should be decided before the corresponding design promises behavior that the current lifecycle does not provide.