No account found
A super admin must create the exact email address first. Email comparison is normalised, but use the corporate address from the invitation.
Complete application guide
Susan User & Administrator Manual
How to submit, validate, manage, and automate data workflows in Susan Data Manager.
Updated
6 September 2026
End users
Submit files and forms, run processes, refresh reports, and understand results.
Template owners & admins
Build templates, rules, automation chains, and review owned execution logs.
Super admins
Manage users, SQL servers, Fabric connections, all executions, and audit logs.
01
About Susan
Susan is a controlled data-management portal. Users work from named templates instead of having to know a database, table, stored procedure, or Fabric element. A template can collect a file, present a structured form, run a process, or refresh a report.
Upload fileExcel or CSV submission, mapping, validation, and import.
Open formGuided entry for comments, FTE, churn, demand, retention, and revenue share.
Run processSequential SQL stored procedures with live events and results.
Refresh reportPower BI semantic-model and dataflow refresh groups.
What end users see: template name, action, and a matching icon. Server names and technical template types are kept out of the normal submission journey.
02
Sign in and navigation
- Open Susan and enter the email address registered by an administrator.
- Select Send Login Code. Susan emails a six-digit, single-use code.
- Enter the code and select Verify & Sign In. Codes remain valid for 30 minutes.
- If necessary, use Use a different email and request another code. A new code invalidates an earlier unused code.
Passkeys
When passkeys are available, sign in once using email or company SSO, then open your user menu and select Security. Enter a name for your passkey, select Add a passkey, and follow your browser's fingerprint, face recognition or PIN prompt. You can add a second passkey for another device or security key.
Next time, choose Sign in with a passkey on the sign-in page. You will not need a login email. If your browser does not support passkeys, the other sign-in options remain available.
If you cannot use your passkey, sign in with an email code. After signing in, open Security to remove a lost passkey or add a replacement. Administrator accounts that require company SSO must continue to use SSO.
You can enrol directly while signed in, without signing in again. To add a passkey on your phone, choose Create QR code in Security and scan it with your phone’s camera. Removing a passkey signs out your other sessions and cancels unused enrolment links. Administrator accounts that require company SSO continue to use SSO.
Newly invited users automatically receive a passkey onboarding email. Setup is optional but strongly recommended. Open the email link to start setup without signing in, then approve with Windows Hello, your device PIN, fingerprint or face recognition. Onboarding links work once and are valid for 7 days. Super admins can choose Enrol a user in their account menu, or Send onboarding beside a user without a passkey, to send a replacement email. A key icon beside each user shows whether they have enrolled. Keep onboarding links private.
Header controls
| Control | Purpose |
|---|---|
| Susan logo | Return to the home screen. |
| Theme | Switch between light and dark mode. The choice is saved in the browser. |
| User profile | See the signed-in email and role, or sign out. |
| User Manual | Open this guide in a separate browser tab. |
| Admin links | Templates, Execution History, Rules, and—where permitted—Servers, Fabric Connections, and Users. |
03
Find and open a template
- Use Search templates to search by template or configured server name. Searching is performed by the backend, so large template lists do not have to load first.
- Use Template action to show Upload file, Open form, Run process, Refresh report, or uncategorised templates.
- Select a tile to start. A Yours badge marks a template you own.
- Susan loads twelve templates at a time. Scroll to load the next page automatically or select Load more.
Users see only explicitly assigned templates. Admins also see templates they created. Super admins see all templates. If no template is available, contact the template owner or a super admin.
Super-admin server tiles
Super admins may also see SQL server tiles. Selecting one opens the table browser and shows a connection badge. Use the badge’s Disconnect action to leave that server context.
04
Submit data through a file template
Choose template→Add context→Choose file→Select sheets / map→Validate→Confirm
- Complete any Additional Information fields. Fields may be text, number, boolean, date, a predefined dropdown, or an automatically filled current month (for example, Sep 2026).
- Select the requested
.xlsxor.csvfile. A specialised template may accept only one of these formats or require several files. - Select Upload File(s). The viewport-level wait screen locks the page only while Susan receives and prepares the source submission.
- For a workbook with multiple sheets, select the sheets to process. Direct templates can then show a source-to-destination column mapping and a sample preview.
- Review record counts, metadata, mapping, and validation results. Select the appropriate Confirm import or Import All button.
Import behaviour
| Method | What it does | User impact |
|---|---|---|
| Insert | Adds incoming rows to existing data. | Existing rows remain. |
| Replace by Key | Replaces rows matching the configured key columns, then adds the submitted rows. | Check that the selected context/key is correct. |
| Full Replace | Validates and stages the complete submission before replacing the destination contents. | The submitted data becomes the full current dataset. |
Do not refresh or submit twice while an upload is being prepared. If Susan reports that another write or process is already running, wait for that operation to finish and try again.
05
Template workflow catalogue
The tile’s action is intentionally simple. The template name and the page that opens tell you which workflow to follow.
Upload file
Direct upload
Upload Excel or CSV, select workbook sheets, map source columns when requested, preview the data, and confirm. The owner chooses Insert, Replace by Key, or Full Replace.
Upload file
Processor uploads
Processors transform a known workbook structure before import. Available processors are KPI Bowler, Sources of Revenue, Organic Revenue Growth & Volumes, and Financial Metrics Matrix. Single-sheet files open a preview; multi-sheet files open sheet selection and tabbed results. Where offered, Download JSON exports the parsed preview.
Upload file
Inventory Data Submission
Upload a workbook and assign sheets to Product Master Data, 12M Consumption, and Current Inventory. Review each dataset’s mapping and preview, then import them together. The owner can configure Insert or Replace by Key.
Upload file
Web Analytics Targets
Upload a CSV file and select the required Business Unit and Year. Susan applies those selections to the mapped destination columns for every imported row.
Upload file
Web Targets Workbook
Upload an XLSX workbook, select the discovered tabs, and verify or override Country, Cluster, Segment, and Brand per tab. Choose full-year replacement or limit the import to selected workbook months, and optionally keep decimal target values instead of the default whole-number rounding. Review added, updated, and deleted SQL values before approval. The final step creates one of seven rolling backups and performs the exact replacement atomically; any listed unmapped rows are skipped.
Upload file
HFM Account Mapping
Upload one .xlsx workbook, then assign workbook sheets to HFM Chart of Accounts, HFM Custom 2, and HFM Custom 4. Review the three tabs and import all.
Upload file
HFM Mapping Rule
Attach all three required workbooks—Account, Custom4, and ICP. Select one sheet from each file, review generated results, and confirm. Susan writes the configured Account, Custom4, ICP, and UD4 IN outputs.
Open form
FTE
Select Month, Year, Business Unit, and Department; enter the FTE value; then select Save FTE. The same Month + Year + Business Unit + Department combination cannot be entered twice. Activity History shows previous entries.
Open form
Comments
Select Year, Month, and Page Name, then load the context. Add or edit rich-text Header, Footer, and Content Description. Existing comments for the context can be edited or deleted.
Open form
Revenue Share %
Enter Year and Month and select Load. Complete and save each of the four tabs separately: % of Region, % of Region Product Revenue, % of Revenue, and Revenues Represented.
Open form
Churn
Select Business Unit and Year. Enter monthly Target and/or Actual values for the configured BWC and BFC hierarchy. Parent and cumulative values are calculated and read-only. Select Save when finished.
Open form
Demand Metrics
Select Business Unit and Year. Enter monthly values at the editable Legal Entity → Product → Metric level. The Totals section updates from the leaf values. Locked month columns cannot be edited.
Open form
Retention
Select Business Unit and Year. Enter monthly Target and Actual values for the configured metrics, then save. Calculated fields and locked months are read-only.
Run process
Stored Procedures
Select Run All. Procedures execute in their configured order. The live status shows Pending, Executing, Completed, or Failed; event timestamps; elapsed time; the first returned result; and any SQL error. Execution stops at the first failed procedure.
Refresh report
Power BI Refresh
Select Run All. Refresh groups run in order, while elements inside one group refresh in parallel. The page shows group and element status, the active job, previous jobs, IDs, timings, and errors.
06
Results, validation, and upload history
Validation failures
If validation fails, Susan does not confirm the import. The error view identifies the rule, description, source line/value, and sheet where applicable.
- Note each error’s row, column/rule, value, and sheet.
- Correct the source file.
- Select Upload Again and resubmit the corrected file.
Successful imports
A success banner or Import Complete page shows inserted record counts. Multi-sheet and multi-dataset imports show a result for each part.
Upload History and Activity History
File templates show immutable Upload History with submission time, user, file/sheet, correlation ID, and metadata. Where available, Edit Metadata updates contextual values. Form templates may show a workflow-specific activity table instead.
07
Template chains and execution history
After a source template completes successfully, Susan can start one or more Stored Procedures templates automatically. Follow-up templates run sequentially in the configured chain and may themselves start later Stored Procedures templates.
Source succeeds→Run queued→Template 2→Template 3→Complete / fail
- The submission page does not wait for the whole chain. Its wait screen covers the source upload/save only.
- The chain runs in the application background and keeps one run context for every later step.
- Values persist through all subsequent levels, not just the immediate next template.
- If the same stored-procedure template is reached more than once in one run, Susan executes it once.
- A failed procedure stops the remaining chain and records the failure.
Values available to later templates
| Source workflow | Captured context examples |
|---|---|
| File upload | Every Additional Information field, Correlation ID, File Name |
| FTE | Year, Month, Business Unit, Department, FTE |
| Comments | Year, Month, Page Name |
| Revenue Share | Year, Month |
| Churn / Demand Metrics / Retention | Business Unit, Year |
| Every chain | Source Template ID, Source Template Name |
Trigger users, template owners, and super admins review these runs in Execution History. The list shows source, trigger user, status, duration, and event count. The list refreshes automatically, while an active detail page updates its status, duration, error, and ordered event log in place without reloading the page.
08
Database table browser
This module is available when a permitted user has an active SQL server context. The sidebar searches and lazy-loads accessible tables by schema.
| Function | How to use it |
|---|---|
| Browse & paginate | Select a table from the sidebar, then use Previous and Next below the rows. |
| Search current page | Type in Search rows to filter the rows currently displayed. |
| Column filters | Add filters using Contains, Equals, Starts with, >, <, Is Null, or Is Not Null, then Apply. |
| Insert | Expand Insert New Row, fill non-identity columns, and submit. Validation rules run first. |
| Edit a cell | Double-click an editable cell, enter a value, then press Enter. Press Escape to cancel. |
| Select / bulk update | Select rows, choose Bulk Update, select one column, and enter the new value. |
| Delete | Delete selected rows, filtered rows, or—after explicit confirmation—all rows. |
| Upload Data | Open the table upload workflow to import a file directly into the selected table. |
| Export CSV | Download all rows matching the active server-side filters. |
| Favorite | Mark the table as a personal favourite. |
| Audit Trail | Review recent recorded changes to the table. |
| Notes | Read or save a shared note describing the table. |
Delete Filtered and Delete All are destructive. Read the confirmation prompt and active filter count before continuing.
Administration
Template Owner, Admin & Super Admin Guide
09
Roles and access model
| Capability | User | Admin / owner | Super Admin |
|---|---|---|---|
| Use templates | Assigned | Assigned + owned | All |
| Manage templates | — | Owned | All |
| Manage validation rules | — | Owned resources | All |
| Lock form months | — | Owned template | All |
| Execution History | Runs they triggered (read-only) | Triggered + owned runs | All runs |
| Users & table permissions | — | — | All |
| SQL servers | As granted | — | Manage all |
| Fabric credentials/connections | — | — | Manage all |
“Owner” means the admin account recorded as the template’s creator. Assigning an admin as an allowed user lets that admin run the template but does not transfer ownership.
10
Manage templates
Open Templates from the header. Search by name, server, or destination; filter by technical type; and load further pages as required. On the home screen, owners can enable Only templates I own alongside the action filter. Select the edit icon to change an owned template or New Template to create one.
Common configuration
Use Clone on any template card, or Clone Template while editing, to open a prefilled copy. Adjust the name and parameters, then select Create Clone. All template types support cloning. The new template belongs to you and retains the reviewed settings, allowed users, follow-up actions, template validation rules and automatic period-lock policy. Destination data, execution history and manual month locks are not duplicated. Server and destination references initially match the source; change them when you need a different destination.
- Set a clear Name, the Connected Server, and the technical Type.
- Complete the type-specific destination, mapping, hierarchy, procedure, or refresh settings.
- Add Metadata Fields. Property types are string, number, boolean, date, predefined, or Current month (MMM YYYY). Current month automatically stores the upload month as text; editing metadata later preserves the original month. For predefined and boolean dropdown values, choose No Order, A-Z, or Z-A. These values are stored with the upload and become chain context.
- Optionally set a positive Reminder interval in hours, days, weeks, or months. Leave the number empty to disable reminders.
- Add Allowed Users by email. Super admins already have global access and are not added here.
- Save and test the template with a representative file or form entry before assigning it broadly.
Type-specific configuration reference
| Type | Owner configures |
|---|---|
| Direct | Destination, Insert / Replace by Key / Full Replace, key columns. |
| Price Update | Destination and allowed Business Units. Missing destinations are created with Business_Unit, Item_Id and Price. Uploaders map the item and price columns from Excel or CSV; each import replaces one Business Unit. |
| Processor | Processor A–D, destination, processor-to-table column mapping. |
| Comments | Destination, Page Name choices, comment-column mapping. |
| FTE | Destination/mapping, Business Units, Departments. |
| Churn | Destination, Business Units, three-level field tree, leaf value type. |
| Demand Metrics | Destination, Business Units, Legal Entity / Product / Metric hierarchy. |
| Retention | Destination and Business Units. |
| Web Analytics Targets | Direct destination/method/mapping and Business Units; ensure Year and Business Unit metadata are present. |
| Web Analytics Adjustments | Choose countries, available currencies, a required default currency, year range, brands, segments, acquisition channels, sales channels and KPI tabs. Users select an enabled currency and enter monthly adjustments for every channel combination. Managers can lock months and configure automatic locking through Period locking & history. Save includes edits across all tabs; blank clears a value and zero remains zero. |
| Web Targets Workbook | Destination and canonical target-column mapping. Users configure tab selection, detected metadata, rounding, and full-year or selected-month replacement during each import. Full-year scope uses Country + Year + Type; selected-month scope adds the exact Date. The importer keeps seven rolling backups. |
| Inventory | Three destinations and mappings, Insert or Replace by Key, key columns. |
| Revenue Share | Four destination tables and their mappings. |
| HFM Account Mapping | Three destination tables and column mappings. |
| HFM Mapping Rule | SKA1 source and Account, Custom4, ICP, and UD4 IN result tables/mappings. |
| Stored Procedures | Procedure reference, business label, description, parameter bindings, execution order, automatic retry count (0–5), and first retry delay. |
| Power BI Refresh | Credential profile values and ordered refresh groups built from Fabric connections. |
Automatic table creation and mappings
When supported, Susan can create a missing destination using the expected schema. If automatic creation is unavailable, the form displays a copyable CREATE TABLE script. When a table already exists, map each logical/source field to the correct destination column; duplicate destination mappings are blocked.
Month locks
Owners and super admins can use the lock icon in Churn, Demand Metrics, and Retention headers. Locks apply to the selected year and make the month read-only. Demand Metrics and Retention locks affect every Business Unit for that year.
Deleting a template is destructive configuration work. Confirm its assignments, rules, chain references, and history needs before deleting it.
11
Configure Stored Procedures and template chains
Create an automatic procedure template
- Create a template with type Stored Procedures.
- For every row, enter the SQL procedure reference (for example
[schema].[procedure]), a required business label, and an optional description. - Enter one parameter binding per line. Parameter names must begin with
@. - Choose Retries from 0–5 and the First delay. Susan classifies transient SQL/transport faults automatically and uses exponential backoff; permanent configuration, permission, and missing-object errors fail immediately.
- Add procedures in the exact sequence in which they should execute.
- Save the procedure template, then edit any source template and add it under Run after completion.
- Add multiple follow-up rows to create a sequence. A Stored Procedures template can also have its own follow-ups, creating a longer chain.
- Users only need permission for the source template they open. Follow-up templates execute from the owner/admin-configured chain even when they are not visible to that user on the home screen.
Parameter syntax
| Purpose | Enter in Parameter Bindings | Runtime value |
|---|---|---|
| Forward a dropdown/metadata value | @Business_Unit=Business Unit | The source value, e.g. Poland |
| Forward the selected year | @Year=Year | The source year |
| Use a constant string | @Business_Unit='A' | A |
| Use a string containing an apostrophe | @Label='Director''s view' | Director's view |
| Use an explicit empty string | @Optional='' | Empty string |
Use exactly one equals sign. Correct:
@Business_Unit='A'. An entry such as @Business_Unit=='A' is invalid; older saved bindings may have passed the extra = into the procedure value.Matching and missing values
- Context matching ignores case, spaces, and underscores. For example,
business_unitmatchesBusiness Unit. - Literal values must be enclosed in single quotes. SQL parameter values are bound safely rather than concatenated into the command.
- If a dynamic context key was not captured, Susan omits that SQL parameter. The stored procedure’s SQL default is then used if one exists.
- If the procedure requires an omitted parameter and has no default, SQL Server returns “expects parameter … which was not supplied,” and the chain fails.
- All later templates in the same chain receive the original run context; values are not lost after the first follow-up.
Chain safeguards
Only executable Stored Procedures and Power BI Refresh templates can be automatic follow-ups. Susan prevents cycles and applies owner/super-admin configuration controls. At runtime, permission to open the source template is sufficient: hidden follow-ups still run, but their names, procedure details, and technical errors are redacted from trigger-only users.
12
Manage validation rules
Open Rules to search or filter existing rules by Table or Template. Admins manage rules for owned resources; super admins can manage all rules.
- Select New Rule and choose Table or Template.
- Select the source and column. The source is locked after creation, so create a new rule to move it elsewhere.
- Choose the rule type and supply its value where required.
- Add a clear custom error message that tells the submitter how to correct the data.
- Save and test with one valid and one invalid example.
| Rule type | Rule value |
|---|---|
| Required | No value; the field must be present/non-empty. |
| Regex Pattern | A regular expression the value must match. |
| Min / Max Length | Minimum or maximum character count. |
| Min / Max Value | Minimum or maximum numeric value. |
| Allowed Values | The accepted value set. |
| Conditional KPI Requirements | A condition on a metadata value plus required columns and required values. Use the visual builder; it generates the rule JSON. |
13
Use Execution History
Execution History is the authoritative run log for source submissions that start chains and for standalone process runs. A trigger user sees runs they started in read-only mode; an owner sees runs for their templates; a super admin sees every run.
- Filter by Source Template and status, including Queued, Executing, Cancelling, Completed, Failed, Needs attention, and Cancelled. Select Apply filters; use Clear to reset.
- The run list refreshes automatically without reloading the page. Refresh pauses while the browser tab is hidden.
- Open a run to see start time, duration, trigger user, event count, and any final error.
- Review Run context to confirm the exact values available to every chained template.
- Read the Event log in order. Automatic retry events show the failed attempt and scheduled retry.
- Owners and super admins may cancel an active run. A confirmation panel explains the impact: queued work is skipped immediately and already-running external work is allowed to finish, after which the run becomes Cancelled.
- Owners and super admins may retry a Failed or Cancelled run. Susan creates a linked run with the original immutable context. It begins with the first failed/skipped stage and does not repeat earlier completed work; if every stage of a cancelled run had already finished, the new run starts from the beginning. Needs-attention runs are deliberately not retryable because their previous side effect has an uncertain outcome.
- Active run details update in place and stop polling when the run reaches a final state.
For a parameter problem, compare three things in this order: the Run context key, the Stored Procedure binding text, and the parameter detail on the procedure-start event.
After retry attempts are exhausted—or when a run needs manual attention—Susan queues email notifications for the triggering user and source-template owner. One person receives only one email; owner messages contain technical details while trigger-only messages are redacted. Delivery uses the existing SendGrid configuration and is retried durably by queue reconciliation.
14
Manage users and permissions
Super Admin Open Users to search by email, filter by role, add accounts, change roles, grant table access, or delete accounts.
- Select Add User, enter the email, choose User, Admin, or Super Admin, and invite. If
APP_URLis configured, Susan sends an invitation link. - Edit a normal User to add permitted SQL table names. Admin and Super Admin roles do not use table-level grants.
- Save the role and permissions together. A super admin cannot remove their own Super Admin role or delete their own account.
- Assign template access from each template’s Allowed Users field; table permission does not automatically grant template access, and vice versa.
Deleting a user removes related sessions, login codes, and permissions. Reassign owned templates and rules before removing an admin account.
15
Manage SQL Server connections
Super Admin Open Servers to add, edit, assign, and delete reusable SQL Server connections.
- Select New Server.
- Paste an ADO.NET-style connection string, or enter Display Name, Host, Port (default 1433), Database, Username, Password, and Trust Server Certificate manually.
- Save, then edit the server card to assign users where direct server/table access is required.
- Editing a server closes its existing application pool so the next request uses the new settings. Leaving Password empty during edit keeps the stored password.
Credential handling and key rotation
Passwords are encrypted before storage. Use the server re-encryption action after rotating the application encryption key. Test the new key and connection before removing the old deployment configuration.
Deleting a server affects every template that points to it. Move or retire those templates first.
16
Manage Fabric credentials, connections, and refresh groups
Super Admin Fabric authentication and Fabric elements are deliberately managed in separate forms.
1. Add reusable credentials
- Open Fabric Connections and select Add Credentials.
- Enter a recognisable Profile Name, Tenant ID, Client ID, and Client Secret.
- Save the profile. Secrets are masked in lists and can be reused by many connections.
2. Add Fabric connections efficiently
- Select Add Connections and choose one Credential Profile.
- Search and select one Workspace. These two settings apply to every element in the form.
- For Element 1, enter a connection name, choose Semantic Model (Dataset) or Dataflow, select Auto/V1/V2, and search for the Fabric element.
- Select Add Element to add more targets from the same workspace without reselecting credentials or workspace.
- Save. Susan creates one reusable connection for each element row.
3. Build a Power BI Refresh template
- Create or edit a template of type Power BI Refresh.
- Select a credential profile or provide its tenant/client/secret values.
- Add refresh groups in execution order and select one or more compatible Fabric connections in each group.
- At runtime, groups execute sequentially and the connections inside a group execute in parallel.
Deleting a credential profile breaks its link from dependent Fabric connections. Reassign or retire those connections first. Rotating a client secret should be planned across every dependent refresh template.
17
Browse Audit Logs
Super Admin Open Logs to browse the existing audit records for user actions, data writes, connections, and configuration changes.
- Search across users, actions, targets, files, details, and recorded errors.
- Filter by a specific action, user email, and Success, Failed, or general Activity outcome.
- Use From and To dates to restrict the UTC time window; the To date includes the whole selected day.
- For Demand Metrics, Churn, Retention, Revenue Share, Comments, and FTE entries, expand Review changes to see the form scope and each recorded Field, Context, Before, and After value. Month lock and unlock actions are recorded too.
- Expand Transaction details for recorded source, destination, row count, data size, and error information.
- Use Previous and Next to browse the server-paginated result set.
Form auditing does not make a successful save depend on an additional comparison query. If Susan cannot read the earlier values, the audit entry is marked accordingly and shows the submitted values. Very large submissions retain the first 250 field changes and state how many additional changes were omitted.
This global page and a table's Audit Trail use the same existing audit records. Use Execution History instead when you need the ordered steps and parameters of a template chain. Runtime service output remains in the local console or Google Cloud Logging.
18
Troubleshooting
Invalid or expired code
Codes expire after 30 minutes and are single-use. Request a new code and use the most recent email.
No templates shown
Ask the owner to add you under Allowed Users. An admin also sees templates they own; super admins see all.
File type rejected
Use the format required by the template. Web Analytics requires CSV; Web Targets Workbook and HFM Account Mapping require XLSX; HFM Mapping Rule requires all three files.
Validation failed
Correct the reported source row/value and upload again. If the rule appears wrong, give the owner the template, sheet, line, rule, and value.
Parameter was not supplied
The context key was absent or misspelled and SQL has no default. Check Run context and bind it as @Parameter=Context key, or use a literal such as @Parameter='A'.
Value starts with “=”
The binding contains an extra equals sign. Change @Param=='A' to @Param='A'.
Another operation is running
Susan serializes concurrent writes to the same destination table and runs stored procedures one at a time. A background procedure does not prevent a new form save, and every successful save creates its own queued chain run. SQL Server can still delay or reject a save if the procedure itself holds a native lock on the same data.
Chain failed
Open Execution History and locate the first failed event. Transient SQL, connection, and transport failures use the procedure's configured retry count automatically. A result row containing a non-zero ERROR_NUMBER is treated as a real procedure failure even if the procedure swallowed the SQL exception. After correcting a permanent error, an owner or super admin can retry from the failed stage without repeating completed work. In local mode, queued work is recovered automatically after Susan restarts.
Power BI job appears interrupted
Reload the refresh page. Persisted in-progress jobs are recovered when the application starts or receives traffic; the Jobs section shows the final state.
Access denied
Template, server, table, owner, and role permissions are separate. Ask a super admin to verify the relevant assignment.
What to send support
Include template name, timestamp, signed-in email, correlation/run/job ID, source filename, and the exact displayed error. Never send database passwords or client secrets.