Use Portal assistant, approvals, and briefing
Use Portal’s assistant-oriented surfaces as decision support while independently validating approvals, sources, and high-impact actions.
Audience, roles, and scope
Portal assistant, approval, and briefing interfaces; not a replacement for the authoritative source system or organization policy.
Who this is for
- Portal users with enabled assistant surfaces
Roles
- Requester
- Approver
- Portal user
Before you begin
- The relevant feature enabled
- Authorization for the underlying information or approval
Article tags
- assistant
- approvals
- briefing
- ai
- preview
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Review an assisted item
Validate context before relying on an assistant summary or making an approval decision.
- 1Open the relevant item
Choose an assistant conversation, approval, or briefing entry and confirm its tenant, owner, and timestamp.
- 2Verify the evidence
Open available source details and compare material facts with the authoritative system before deciding or acting.
- 3Take a governed action
Approve, reject, or continue only within your role; record a clear non-sensitive rationale when the interface allows it.
The assisted information is independently checked and any decision stays within the user’s authority.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Do not place credentials, secrets, or unnecessary personal data in assistant prompts or approval comments.
- Human accountability remains with the person making the decision.
Known limitations
- Assistant, briefing, and connected approval behavior is beta and depends on configured data sources and services.
- Generated summaries can be incomplete or incorrect; visible output is not an authoritative audit record by itself.
Troubleshooting
You cannot open Vianordis Portal
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
The three Portal surfaces and their visible interactions were reviewed; connected data and automation vary by deployment.
Reviewed paths at e7035d9
src/structure/PortalShell.tsxsrc/lib/agent-portal.tssrc/app/api/chat/briefing/route.tssrc/app/api/chat/approvals/route.ts
Contact support
Contact support when
- A repeatable Vianordis Portal error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel