Account Settings
Account Settings is the user-level configuration area in AssureGrid. It helps each user maintain accurate account information, review personal preferences, and manage the parts of their AssureGrid experience that are meant to be self-service, while keeping access governance under administrative control.
At a glance
Allow users to manage personal account information and the settings relevant to their own AssureGrid experience.
All authenticated AssureGrid users who need to review or maintain their account-level details.
Profile details, selected preferences, and user-level maintenance actions where those items are available for self-service.
Role changes, broader permissions, and organizational access alignment are typically handled by an administrator rather than through Account Settings.
Core principle: Account Settings supports personal maintenance, not access governance. Use it to keep your user profile accurate; use administrators for role and workspace changes.
What Account Settings is for
Account Settings gives users a dedicated place to review and maintain the parts of their platform profile that belong at the individual-account level. This helps users keep their identity and preferences current without mixing personal maintenance with broader administrative responsibilities.
In AssureGrid, that distinction matters. The platform is built around controlled access to audit artifacts, planning records, evidence, workpapers, issues, and reports. Users may manage some elements of their own account, but the overall access model should still remain governed centrally.
What users can typically manage
| Category | Purpose | Notes |
|---|---|---|
| Profile information | Keep user identity details current and accurate. | Some fields may be editable directly, while others may be managed centrally depending on configuration. |
| Contact or notification preferences | Align communications and alerts with how the user works. | Availability may vary by deployment or administrative setup. |
| Sign-in-related settings | Maintain user-level security or sign-in details where self-service is allowed. | In some organizations these settings may be controlled outside AssureGrid. |
| Session and logout actions | Help users manage current sessions and end access when work is complete. | This is especially important on shared or temporary devices. |
| Help or support access | Provide a path to assistance when account questions arise. | Support access does not replace administrator-managed permission changes. |
What remains admin-managed
A useful way to understand Account Settings is to know what it does not control. Even where users can update personal details, that does not mean they can independently change their permission model or organizational visibility.
-
Roles and permission scope: Administrative ownership should determine what a user can do across the platform.
-
Team or workspace membership: Organizational alignment usually requires admin action because it affects collaboration boundaries.
-
Module visibility: Whether a user can access specific modules should remain part of governed setup.
-
Organization-level policies: Broader security, governance, and configuration settings are outside normal self-service account maintenance.
-
Exception access decisions: Temporary or elevated permissions should be reviewed through formal administrative processes.
Recommended user maintenance routine
Users can keep their AssureGrid experience cleaner and more reliable by treating Account Settings as a lightweight maintenance checkpoint rather than something they visit only when a problem occurs.
-
Review settings after onboarding: Confirm that profile information and any visible preferences are correct when access is first established.
-
Recheck after responsibility changes: If a user’s role changes, make sure personal profile details still reflect the current context even though broader access changes may be handled elsewhere.
-
Verify account information before major audit activity: Accurate account details support smoother collaboration and support if questions arise.
-
Use logout and session discipline: End sessions appropriately, especially when working in shared environments or between multiple devices.
-
Separate profile maintenance from access requests: If the problem is really about permissions or visibility, route it through the right administrative process.
Frequently asked questions
Does changing Account Settings change my role or permissions?
No. Account Settings is meant for user-level maintenance. Broader access, module visibility, and organizational alignment are usually managed administratively.
Can I update every field about my account myself?
Not necessarily. Some fields may be editable directly, while others may be controlled by administrative or organizational configuration.
Why can I sign in but still not see the workspace I need?
Because authentication and account maintenance are separate from workspace or role assignment. The issue likely requires an administrative access review.
Should I use Account Settings to request broader access?
Account Settings is generally not the best place for access expansion. Requests for new permissions or workspace visibility should follow the appropriate governance path.
How often should I review my Account Settings?
A good pattern is to review them during onboarding, after responsibility changes, and whenever account information or user preferences may have become outdated.