Signing in, and who to be#

Timberline ships an administrator seat and eight business accounts. Which one you are acting as changes what you can do and what you can see, which is the point, "what does this look like for the person receiving it?" is a question the demo is built to answer.

There is only one seat you can actually sign in as. The administrator account is the one with a password; the eight business accounts have no password set at all, so signing in as a contributor or an approver is not possible. To see what they received, read the demo inbox instead, below. Ask your Reportworq contact for the demo administrator credential.

The seats#

The demo carries a small identity model, deliberately shaped so that scope is visible: change the seat, change what is in scope.

Seat	Scope	What it is for
Administrator	all workspaces	Start here. Authoring and configuration. Every job and campaign in the demo was built from here, and it is the only seat you can sign in as.
Leadership	company-wide	A business seat with company-wide scope. The budget campaign sends its invitations from this seat.
Regional and territory seats	one region each	Six of them, each in its own group, so a group maps to exactly one scope. That is what makes secured lists demonstrable.
Contributors	one market each	Three of them, one per generated budget form.
Approvers	one or more markets	Two of them. One approver covers both US markets, which is the more realistic shape: approval rarely maps one-to-one onto entry.

Each group has exactly one member. In a real deployment groups hold many people; here the one-to-one mapping keeps the demo legible.

Ask your Reportworq contact for the account list. Which named account holds which seat is not published here. You do not need it to follow this guide, and the roles above are what the configuration actually keys on.

What each seat can do#

Entitlement	Who has it
Administrator	the administrator seat
Workspace Member	all eight business accounts
User	the region and function groups
Author	nobody

Two things to know before you demo from a business seat:

Nobody holds Author. The business accounts can read, contribute and refresh PowerPoint, but they cannot author. If you want to show authoring from a non-admin seat, grant the entitlement first.
Contribution and PowerPoint are not separate entitlements. Both are capabilities of the User role. A User participates in contribution campaigns when the installation licenses the Contribution capability, and any User can refresh a distributed PowerPoint deck in the add-in. See Licensing and entitlements.

The demo store predates the entitlement consolidation. It was built when the roles were named System Administrator, Reader, Contribution End User, and PowerPoint End User. Those grants are still in the store, but the product now shows you Administrator, Author, User, and Workspace Member. If you are reading the raw store rather than the Security screen, expect the older names. See Roles and what you can do.

Seeing it as somebody else#

Just read their mail#

Usually the fastest, and it needs no seat switching at all. Because email runs in demo-inbox mode, everything the jobs have ever delivered is sitting in an inbox inside the application, addressed to whoever received it, with the embedded screenshots, HTML tables and AI commentary intact.

Use this for: "show me what they actually got".

Everything scopes per user#

The point the demo is built to make is that scope follows the person, not the screen. A regional seat sees its own region in a secured list; a contributor sees their own form; AI and integration access answer within the same boundary rather than around it. You do not have to switch seats to believe it, the demo inbox already shows the same job producing different content for different people.

Switching seats is an administrator facility. The business accounts have no password set, so there is no signing in as them. Ask your Reportworq contact to show you the contributor and approver experience directly.

Recipients are not users#

This trips people up. The jobs resolve their recipients from the planning model, not from the account list, the workbook looks the address up from the employee dimension. So the demo inbox contains mail addressed to people who have no Reportworq account whatsoever.

That is correct, and it is worth saying out loud in a demo: a report recipient does not need to be a user. Only people who sign in, contributors, approvers, readers, need accounts. It is usually a licensing question in disguise.

The campaign catalog, how the forms are assigned
Build a compelling email dashboard, what is in that mail

Feedback on this page

Comments, questions, requests, or something missing or unclear? Email us - the page you are on is filled in for you.

Email feedback on this page

Or write to support@reportworq.com directly.