Client Dashboard Features

New client users and account administrators

Creates the account context, user access and initial relationship records needed to begin using the platform.

Boundary: It does not replace project discovery or confirm that every requested integration is ready.

Clients requesting work and staff preparing a commercial response

Records an estimate or quote request, the response, its state and any later commitment to proceed.

Boundary: A ballpark indication is not a committed scope; the record must reach the appropriate agreed state.

Authorised client users exploring available services

Helps assemble and request a combination of services from the options available to the account.

Boundary: The output is an enquiry or configuration input, not an automatically accepted project specification.

Client users who need a discussion with the team

Creates a structured request for a meeting and keeps it attached to the account.

Boundary: Submitting a request does not guarantee a particular time until it is confirmed.

Clients raising work and the team triaging it

Captures the brief, status, history and ownership of a request before and during delivery.

Boundary: A request is not automatically approved, estimated or scheduled simply because it has been submitted.

Clients and team members resolving a specific question or blocker

Keeps a question, response and resolution state separate from a general work request.

Boundary: Queries are for clarification and tracked issues; substantial new work should become a scoped request.

Authorised clients and the delivery team

Shows the projects connected to an account and the delivery context made available for each one.

Boundary: Client visibility is not the same as access to every internal repository, task or management field.

Digital Royalty delivery roles

Organises accepted work into backlog and sprint states used by the team to plan execution.

Boundary: It is primarily an operating control; a client should judge the agreed outcome and relevant status, not administer the team backlog.

Staff and approved delivery roles

Records time against clients, projects and work so delivery and allocation can be reviewed.

Boundary: A raw time entry is an internal operational record unless the engagement explicitly makes a summary client-visible.

Users with the relevant report permission

Presents selected delivery, time, fulfilment or system-status information from records held by the platform.

Boundary: The available report depends on the services, data sources and permissions configured for the account.

Signatories and staff managing the agreement

Tracks contract preparation, signature state and the stored record through the SignWell integration.

Boundary: The Dashboard shows and coordinates the record; the signed agreement remains the authority on scope and terms.

Authorised client users with billing access

Provides account-specific access to the billing and payment records made available through the platform.

Boundary: Payment processing and card handling rely on Stripe; access does not remove the processor's own terms or fees.

Clients reviewing invoices and staff issuing them

Connects invoice creation and status to the relevant client account and commercial workflow.

Boundary: An invoice does not define unrecorded project scope, and accounting treatment remains the responsibility of each party.

Users managing an enabled recurring product or service

Records subscription state and uses entitlements to control access to connected Beacon products.

Boundary: The existence of a product slug in the platform does not prove that the corresponding product is ready for public sale.

Client account administrators

Lets an authorised user invite and manage additional people associated with the client account.

Boundary: Delegation should follow least-privilege access; an invite does not need to grant every account capability.

Account administrators and Digital Royalty administrators

Gates routes and actions according to the user's role, account and assigned permissions.

Boundary: Permissions reduce exposure but do not replace secure devices, credential hygiene or operational review.

Authorised users exchanging credentials for delivery work

Provides a controlled route to store or reveal account credentials instead of sending them through ordinary messages.

Boundary: Only credentials genuinely needed for the work should be shared, and access should be removed when it is no longer required.

Accounts and workflows configured to use an external provider

Connects specialist services such as payments, e-signatures, notifications and product APIs to the relevant workflow.

Boundary: An integration in the codebase is not evidence that every client account uses it or that the third party is always available.

Accounts with monitoring configured

Stores monitored URLs, check history and an account view of availability results.

Boundary: It is not a guarantee of uninterrupted service; check frequency, alerting and incident response must be agreed separately.

Users with tool access and available usage credit or entitlement

Runs defined AI-assisted tasks and keeps access and run history inside the account.

Boundary: Outputs require review, and metered provider usage may create a separate charge.

Clients with an agreed agent workflow

Provides settings and operating surfaces for a bounded agent configured around approved tools, knowledge and escalation rules.

Boundary: It is not switched on as a general autonomous worker for every account; setup and human handoff are part of the product boundary.

Digital Royalty staff with the relevant permission

Maintains an internal procedure library used to make recurring delivery work more consistent.

Boundary: Internal SOP access is not part of the client workspace and the library is not sold as a client knowledge product.

Current or prospective Digital Royalty clients

Supports an ongoing working relationship where requests, delivery and commercial records need one dependable home.

Boundary: It is not a standalone SaaS portal for businesses that are not working with Digital Royalty.