Questions, answered

Click Get started, then use Proto to configure SaaS Management Platform for your business. Begin with one active service, one subscription, named owners and a representative access request.

The subscription links to a person who owns its renewal discussion. Individual usage records link to the people allocated access.

Compare assigned, last active and revoked dates on usage records against the subscription’s licensed seats. Confirm the source and freshness of activity dates during setup.

Record it as a service request with requester and service. The Service Manager decides approval; the manager records request completion after the technician performs the work and updates the affected allocation.

An incident can reference an affected asset and service. The asset keeps its own location and status while the incident carries response dates and updates.

The Change Approver reviews the change’s risk, schedule and rollback plan before implementation.

It records the provider event identity, received time, payload hash and processing outcome. Review the target business record to confirm the intended result.

Use a problem record for the service, owner, problem statement, root cause and investigation status. Keep each incident’s own response history.

Reports read subscription, usage, service work and receipt records. Their dates and statuses should be checked against the underlying items.

Set up people, roles, one service and one subscription. Then rehearse a request decision, incident chronology and reviewed change before widening the portfolio.