Coworking access rights
Connect time or visit credits with reservations and facility access.
The scenario
ForCoworking, shared-office and shared-facility operators
Grant single-visit credits and redeem them when entering a reserved facility. Integrate reservations, keys and entry/exit through facility systems.
What this makes visible
Align remaining credits, reservations and actual visits so operators can inspect usage history.
Token and business-data roles
Represented by tokens
Manage visit quantities by type with PrivilegeEdition. Keep room, seating and time-slot rules in the reservation system.
Managed in business systems
Member/facility IDs, reserved slot, pricing plan, entry/exit records and usage request ID.
Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.
Contract composition
| Contract | Role in this use case |
|---|---|
| PrivilegeEdition | Manage issuance and redemption of access credits. |
| Whitelist | Represent member or user eligibility. |
Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.
User and processing flow
Configure the plan
Define facilities, times, visit quantities and reservation conditions.
Grant credits
Issue credits for the plan and link order, member and token.
Authorize a visit
Verify reservation and balance, then connect approved redemption to entry permission.
Record usage
Record completion or cancellation and reconcile balances with facility history.
Operating considerations
Access-device integration
Smart-lock control belongs to the facility integration. Define operating rules for access during connectivity failures.
Concurrent usage
Identify reservations and redemption requests to prevent simultaneous use of the same credits.
Implement this use case
These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.