Getting started with Osinet Command

Go to the sign-in page and enter your email address. If your organization uses Microsoft SSO, select “Continue with Microsoft” to authenticate via your Entra ID account.

After your first sign-in, your organization owner will assign you a role. Owners and admins see the full portfolio. Customer viewers see only assigned customers.

The MSP overview shows aggregate posture across all customers. Click any customer row to open the per-customer detail view with module-level data from each connected vendor.

You can enroll a TOTP authenticator app (e.g., Google Authenticator, Authy) from your account settings. Enrollment is optional during early access.

Go to Integrations in the sidebar. Each connector (Microsoft 365, Acronis, ESET, SentinelOne, Check Point, FortiGate) has its own setup page where you enter API credentials.

After entering connector credentials, go to the connector's mapping page to link each connector account (tenant, site, customer) to the corresponding customer in your MSP portfolio.

Use the sync button on each connector page to pull a fresh snapshot. Snapshots are stored in Supabase — data persists across sessions and page reloads.

Dashboard cards appear only for connectors that are enabled for your organization. Cards for disabled connectors are hidden automatically — no empty tiles.

Each dashboard card corresponds to a connector module (e.g., backup_health, edr_threats, email_security). Cards are shown only when the backing connector is enabled.

The all-customers view shows aggregate health scores, 7-day incident trends, backup success rate, and per-connector product cards. Severity totals are computed across all customers.

Click a customer to see a focused layout: identity posture (M365), backup status (Acronis), endpoint protection (ESET, SentinelOne), email security (Check Point), and firewall status (FortiGate).

The security score (0–100) is computed from posture signals across all connected modules. Missing connectors reduce the denominator — connect more vendors for a more complete score.

Owners and admins can invite users from the Users page. Enter the email address, choose a role, and optionally assign specific customers for customer viewer accounts.

Owner — full access including billing and user management. Admin — connector and customer operations, no billing. Technician — read access, no configuration. Customer Viewer — read-only, scoped to assigned customers.

Customer assignments are set at invite time or edited post-registration via the user management page. Assignments survive invite resends and SSO registration.

Owners can deactivate or remove members from the Users page. Deactivated members cannot sign in but their audit history is preserved.

Six plan tiers are defined: internal, pilot, starter, growth, pro, and enterprise. Each tier maps to a feature key set.

During early access, billing enforcement is soft. Organizations without an active subscription default to pilot access — no lockout occurs. Stripe checkout integration is planned but not yet wired.

Your current plan and subscription status are visible in the billing section of the Settings page. Owners can view plan details and feature key assignments.

Dashboard cards only appear when a connector is enabled for your org and at least one customer mapping exists. Verify the connector is configured and synced in the Integrations section.

Connector data is snapshot-based. Use the sync button on the connector page to pull fresh data. If a sync fails, check that your API credentials are still valid in the vendor's admin portal.

If you cannot see a customer, verify your role. Customer viewers only see explicitly assigned customers. Contact your organization admin to update your customer assignments.

If SSO login fails, ensure your Microsoft account matches the email address your admin used to invite you. If SSO is unavailable, use the local credential (email + password) path as a break-glass fallback.