In short: The Analysis Scope contextualizes the entire platform around what concerns you: data outside your scope disappears from your analyses. You build it by combining three dimensions (People, Tech, Process); it applies everywhere, persists across sessions and can be reused in one click.
Prerequisites
No specific role required: every user builds and saves their own scopes.
Saved scopes are personal. Sharing scopes between users will come in a future version.
What the Analysis Scope is for
The platform covers your entire organization: thousands of applications, dozens of domains, whole populations. Yet each user is only responsible for a fraction of it.
The Analysis Scope contextualizes the platform around your reality: everything outside your scope is removed from your screens and your calculations.
You work noise-free, on the data that concerns you.
The mechanism goes further than a filter. A column filter hides rows: the displayed figures do not change. The Analysis Scope changes the data itself: all platform metrics (active users, average weekly time, and so on) are recalculated on the chosen scope.
This is what makes the feature powerful:
You work on your real perimeter: a Domain Owner no longer sees figures for the whole organization, but for their own domain, on every page, without reconfiguring anything. The noise from other perimeters disappears.
You answer cross-cutting questions in a single configuration: "which AI applications are used by Marketing in France?" becomes a People scope (France > Marketing) combined with a Tech scope (AI category), applied everywhere.
Your analyses stay consistent: the same scope feeds all your screens. No more exports and manual cross-checks where everyone computes their own numbers.
The core of the system: three dimensions
A scope is built on the platform's three structuring dimensions. They combine with a logical AND: only the data at their intersection is retained.
People (who): organizational domains. Browsed hierarchically (e.g. Region → Country → Department) or as a matrix (e.g. Country / Organization / Function), depending on your platform configuration.
Tech (what): functional perimeters, via the Beamy taxonomy (Category → Sub-category → Feature), via your Custom Taxonomy (your own categories, sub-categories and modules) when it is configured, or by selecting applications directly.
Process (how): business activities and the tasks performed within the tools themselves.
The scope selector
A scope selector is available in the header of every page concerned, with three states:
No scope: the displayed data covers the whole organization.
Saved scope (blue): the scope is stored in your library.
Unsaved scope (orange): the scope is ephemeral and is deleted at logout. A Save button is offered.
Click the selector to switch between your saved scopes or create a new one. A banner is displayed on every page where the scope applies, as a reminder that the data is filtered. You can hide it by clicking the cross: the scope stays active.
Building a scope
The building panel opens from the selector, with one section per dimension.
People: browse your domains, with a user counter and bulk selection by level. In matrix mode, the three axes intersect with a logical AND and the resulting formula is displayed explicitly.
Tech: browse the Beamy taxonomy or your Custom Taxonomy, or select applications directly.
Process: browse business activities and their associated functional tasks.
Advanced settings: applications in use, detection source (Web Extension (WBE) and/or Desktop Agent).
Apply, save, reuse
Apply activates the scope for your whole session: it follows you from page to page without reconfiguration.
Save adds it to your personal library: renaming, duplication and deletion are available from the selector.
Default scope: star a scope so it loads automatically at every login.
Sharing a scope
A saved scope can be shared with other users, so that a team reasons on the same analysis context. This keeps a single, consistent definition of a scope (for example, "AI Applications – Marketing Europe") instead of everyone rebuilding their own.
ℹ️ Only the author of a scope can edit it. However, other users with access can easily create a copy in order to adapt it to their own specific needs.
How the scope acts on pages
One simple rule governs the whole system: every page has a subject (applications for Apps Inventory, domains for the People dimension, the taxonomy for the Tech dimension, and so on). The effect of each scope dimension depends on its relationship to the page's subject.
On a table page
The dimension that matches the page's subject filters the rows. Example: a Tech scope "AI applications" on Apps Inventory only displays AI applications.
The other dimensions recalculate the metrics of each row. Example: a People scope "France" on Apps Inventory recalculates the active users and weekly time of each application on the population of the France domain only.
On the Dimensions, a Scope row at the top of the table aggregates the metrics of your whole scope: average weekly time, active users, number of applications, top applications.
On a sheet
The dimension that matches the sheet's subject is neutral: it has no effect. On a Product Sheet, the Tech dimension of the scope does not apply (the application you are viewing is the subject).
The other dimensions recalculate the sheet's metrics. Example: on the Google Calendar Product Sheet with a People scope "France", all KPIs, charts and breakdowns are computed on the users of the France domain only.
If you open a sheet outside your scope (through search, a favorite, a link), it is displayed normally. The scope is an analysis and filtering tool, not a permission system: nothing is blocked.
Sub-tables within sheets (for instance "Apps used" on a People sheet) follow the table-page rules: the Tech dimension filters their rows.
Specific pages
On Guidance, settings, automations and Supplementary Sources, scopes do not apply.
Additionally, for this first version, the Organizational Map and Dashboards are not covered yet. They will be in a future version.
Concrete example
A Domain Owner responsible for Marketing in Europe creates a scope: People "Europe > Marketing", Tech "Marketing & Communication", with the advanced setting that excludes applications without users. They save it as their default scope.
At every login: Apps Inventory only shows the applications of their category, with metrics computed on their population; the Scope row gives them their consolidated figures; and every Product Sheet they open reasons on their own users. They can focus their efforts on their work perimeter without having to navigate through all of Beamy's data.