Keep customer workspaces separate
Customer membership, commercial ownership, billing responsibility and delegated operational access serve different purposes. Commercial ancestry alone must never authorize access to logs or credentials.
AOT OpsAI solutions
Build service delivery around clear customer boundaries.
Plan MSP monitoring in the Philippines with separate customer workspaces, scoped operational access, private reports and clear service responsibilities.
A proposed partner path
Discuss distributor, reseller or managed-provider participation with AOT. Partner agreements, wholesale catalogs and public activation remain subject to review. No automatic reseller margin is promised.
Define the operational scope
Agree on permitted customer summaries, report access and support responsibility. Brand and domain verification are separate from data authorization. A reseller logo cannot change a collector’s signing publisher.
Make customer onboarding a repeatable review
Identify the customer owner, authorized operator, site and collection path before adding sources. Use read-only access where supported, review discovered resources and confirm that fresh telemetry arrives. Keep unavailable sources in the handover record. The operator should be able to trace a customer incident to its affected asset and time range without crossing into another workspace or sharing a customer credential.
Separate a technical evaluation from a commercial commitment
During a pilot, test the permissions of both an authorized operator and a user who should have no access. Review report delivery, collector responsibility and the process for removing access. Then agree on plan scope, billing responsibility, support hours and escalation with AOT and the customer. A portal relationship or a working collector is not an executed partner agreement, a credit facility or a promise of an approved margin.