-
Notifications
You must be signed in to change notification settings - Fork 8
Release note: Always Know When You're Acting on Behalf of an Operator #197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| --- | ||
| title: "Always Know When You're Acting on Behalf of an Operator" | ||
| authors: posdealer | ||
| slug: portal/surrogate-context-banner | ||
| milestone: "n/a" | ||
| date: 2026-06-24 | ||
| tags: [] | ||
| --- | ||
|
|
||
| ## Summary | ||
| When you act on behalf of one of your operators, the fiskaltrust Service Portal now shows a clear, persistent banner across every screen — so you always know exactly whose account your actions affect. | ||
| <!--truncate--> | ||
| ## Why This Matters | ||
| As a dealer or consultant, you can step into one of your operators' accounts to help them set things up or resolve an issue. Until now, the portal looked exactly the same whether you were working in your own account or in an operator's — nothing on screen told the two apart. That made it easy to lose track of which context you were in, and to make changes against an operator's account while believing you were in your own. | ||
|
|
||
| The new banner removes that ambiguity. At a glance, and on every page, you can see whose account you are currently working in. It turns a subtle, error-prone situation into one that is obvious and safe — acting as a real safeguard, not just a label. | ||
|
|
||
| ## What Changed | ||
| - Whenever you are acting on behalf of an operator, a banner stays pinned to the top of the portal. It remains visible no matter where you navigate. | ||
| - The banner names the operator and states the consequence in plain language: *"You are acting on behalf of [Operator]. Everything you do here affects only this operator's account."* | ||
| - To leave the operator's context, use **Back to your account** in the top bar. The banner disappears the moment you return to your own account. | ||
|
|
||
|  | ||
|
|
||
| ## Impact | ||
| This update is rolling out for **Austria** and **Germany**, and affects dealers and consultants who act on behalf of their operators. No action is required on your side — the banner appears automatically whenever you are working in an operator's account, and disappears as soon as you return to your own. | ||
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.