Organization settings

Organization settings live at /admin/org/[your-org-id], reachable from the admin area, and are admin-only. Depending on your plan and role you may not see every tab; ask your provider if something you expect is missing. The page is organized into seven tabs: Profile, Members, Roles, Authentication, Integrations, Notifications, and Billing. This article covers Profile, Authentication, Integrations, and Notifications. For the Members and Roles tabs see Members and roles, and for the Billing tab see Billing and plans.

Profile

Your organization’s identity and paperwork. The legal name, domain, alias, tax ID, and headquarters address are all editable inline. This tab also holds:

• Documents. Upload and view your Letter of Authorization (LOA), NDA, and Master Service Agreement (MSA).
• Company contacts. Every contact on file for your organization, which is broader than just portal users. Email and phone are editable inline, and a read-only badge shows which contacts also have portal (login) access.
• GL codes. Shown here read-only for reference. You assign GL codes and cost centers at the service level, not on this tab.

Members and Roles

The Members tab is where you invite teammates and manage access, and the Roles tab is where you configure custom roles and the org permission set. Both are covered in Members and roles.

Authentication

Toggle which sign-in methods your organization allows: Email & Password, Magic Link, Google, Microsoft, and Single Sign-On. At least one method must stay enabled at all times.

You can add and edit your own SAML or OIDC SSO providers right here and then turn SSO on. You do not have to ask your provider to configure SSO for you.

Two enforcement toggles also live on this tab: Require SSO only and Require MFA for all members. Both raise the sign-in bar for everyone in the organization, so plan for them before you switch them on. How enforcement affects individual members, and how they add a passkey or authenticator, is covered in Security and support access and Two-factor and passkeys.

Integrations

Connections to outside systems that other parts of Vigilis rely on. Each integration includes in-app setup instructions and, where relevant, a way to test the connection.

• Lumen Order Contact. The name, email, and phone of your network contact. This is the person Auto-Flux emails when a circuit approaches its change rate limit and reverts once to your standard bandwidth, so keep it current if you use the Network add-on.
• Webhook secrets. Generate the shared secret for LibreNMS and the generic webhook. Each secret is shown once. Vigilis signs and verifies every request against it.
• Monitoring credentials. Store your Meraki (API key and organization ID) or UniFi (API key and host) credentials so Vigilis can pull utilization data.

Notifications

Choose which email addresses your organization copies for five event types: Invoice Received, Disconnect Billing Alert, Contract Expiration, Weekly Digest, and Payment Failed.

These recipient lists are distinct from personal preferences. When an event type has no addresses set here, each user’s own notification preferences apply. Once you add addresses for a type, that type is routed to them organization-wide.