Disabling an Agent account prevents the Agent from accessing SchemeServe or creating new business, but it does not affect existing records already linked to that Agent.

What Happens When an Agent is Disabled?

When an Agent status is changed from Enabled to Disabled:

• Existing quotes, policies, and records remain intact
• Any live policies already on cover are unaffected
• Records allocated to the Agent account continue to exist and remain accessible to administrators

Changing the Agent status does not remove or cancel existing business.

Any records allocated to an Agent account will not be affected by the status of that Agent account being changed from Enabled to Disabled.

Can the Agent Still Access the System?

No.

Once the master Agent account is disabled:

• Agent users can no longer continue using the platform
• Existing sessions are terminated
• Users are logged out automatically when attempting to navigate the site

For example:

• An Agent user remained signed in on another browser session
• The Agent account was changed to Disabled
• When the user attempted to open a policy record, they received a warning message and were logged out of the site

This prevents the Agent from creating new quotes or accessing records after the account has been disabled.

Is It Necessary to Delete All Users?

No.

It is possible to delete all users associated with the Agent account, but this is not normally required.

Disabling the master Agent account is sufficient to block access.

While an Agent account is still enabled:

• users can sign in,
• view records,
• and continue working on the account.

Once the Agent account is disabled, access is prevented regardless of whether individual users still exist on the account.

Recommended Approach

To stop an Agent from transacting new business:

1. Change the Agent status from Enabled to Disabled
2. Leave existing records and policies in place
3. Optionally remove users if additional cleanup is required

In most cases, disabling the Agent account alone is enough.