Every website managed through SimplifyAccess is associated with a controller.
A controller connects your website to the platform and maintains its individual configuration, accessibility information, and resource usage.
If you manage multiple websites, each receives its own controller. This allows you to manage several domains from one account while keeping their settings and accessibility results separate.
The Controllers page is your central location for managing these website connections.
From this page, you can:
- View all registered websites and their Controller IDs.
- Monitor resource usage for individual controllers and your entire account.
- Access widget settings and accessibility statements.
- Configure domains, sitemaps, and developer email addresses.
- Purchase or activate additional website controllers.
- Remove additional controllers when they are no longer needed.
1. Accessing the Controllers Page
Open the Controllers Overview after signing in to your SimplifyAccess account.
The page displays your registered controllers in a list.
Each entry includes:
| Information | Description |
|---|---|
| Website domain | The registered domain associated with the controller |
| Controller ID | The unique identifier used to connect the website to SimplifyAccess |
| API Usage | API requests consumed against the controller's allowance |
| Job Usage | Manually initiated processing operations counted against the controller's allowance |
| Context menu | Additional settings and management actions |
The number of registered controllers is displayed above the list.
Understanding the Controller ID
Every controller receives a unique identifier when it is created.
This identifier is used to associate your website and its integrations with the correct SimplifyAccess configuration.
You may need the Controller ID when integrating the Accessibility Widget, configuring API access, or communicating with support.
Each controller has its own ID, even when multiple controllers belong to the same account.
2. Monitoring Resource Usage
The Controllers page provides two perspectives on resource consumption: individual controller usage and overall usage.
Individual Controller Usage
Each controller displays its own:
- API Usage: Requests counted against its API allowance.
- Job Usage: Manually triggered processing operations counted against its job allowance.
Progress bars help you recognize when a controller is approaching its available limits.
Overall Usage
The Overall Usage card on the right combines resource consumption across your registered controllers.
It provides a visual chart and usage counters for:
| Resource | Description |
|---|---|
| API Usage | Combined API requests across controllers |
| Job Usage | Combined processing job consumption |
| Email Usage | Developer email messages counted against the available allowances |
| Report Usage | Generated reports counted against the available allowances |
If your account has one controller, Overall Usage reflects that website's usage.
If your account has multiple controllers, the card displays their combined usage and allowances.
The combined figures are intended to provide an account-wide overview. They do not replace the individual limits applicable to each controller.
For a detailed explanation of quotas, subscription periods, and resource types, see the guide Understanding Usage and Resource Limits.
3. Using the Controller Context Menu
Each controller has a three-dot menu containing its management actions.
Select the menu beside the relevant website to access the available options.
| Action | Purpose |
|---|---|
| Open widget settings | Configure the Accessibility Widget for the selected website |
| Edit Statement | Create or update the website's accessibility statement |
| Change Domain Name | Change the domain associated with the controller |
| Add Sitemap | Specify or update the website's sitemap path |
| Settings | Open the controller settings sidebar |
| Delete Controller | Remove an eligible additional controller |
The actions apply to the controller whose menu you opened.
Widget Settings
Select Open widget settings to configure the visitor-facing accessibility integration.
Widget configuration is maintained separately for each controller, allowing different websites to have their own settings.
Learn more about the Accessibility Widget.
Accessibility Statement
Select Edit Statement to open the guided Accessibility Statement Editor.
The editor helps you document organizational information, the applicable legal context, accessibility status, known barriers, feedback mechanisms, and publication options.
For detailed instructions, see How to Create, Edit, and Publish an Accessibility Statement.
4. Managing Controller Settings
Select Settings from a controller's context menu to open its settings sidebar.
The sidebar displays three configurable elements:
- Domain Name
- Sitemap
- Developer email
After making changes, select Update to save the settings.
Domain Name
The Domain Name field identifies the website associated with the controller.
If you need to move the controller to another domain, you can update the registered domain.
The context menu also provides a direct Change Domain Name action.
Important: Domain changes are subject to a monthly allowance determined by your subscription.
Before changing the domain, verify that the new domain is correct and that any necessary website integration changes have been prepared.
See Pricing and Plans for the applicable allowances.
Sitemap
A sitemap helps SimplifyAccess discover the pages belonging to your website.
By default, the sitemap path is:
https://your-domain.com/sitemap.xml
If your website uses a different sitemap location, you can specify the appropriate path.
For example:
https://your-domain.com/sitemap_index.xml
or:
https://your-domain.com/content/sitemap.xml
The context menu also provides an Add Sitemap action for accessing this configuration.
Tip: Make sure the sitemap location is correct and publicly accessible. A valid sitemap helps SimplifyAccess discover website pages for subsequent accessibility workflows.
Developer Email
The Developer email field allows you to specify where accessibility-related developer messages should be sent.
This could be:
- Your website developer
- An internal IT department
- A technical support address
- Another person responsible for website improvements
If the field is left empty, SimplifyAccess uses your account email address.
Developer emails are counted as messages sent and are subject to the controller's monthly email allowance.
5. Adding Another Website or Controller
SimplifyAccess allows eligible customers to manage multiple websites within a single account.
The Buy an additional Domain card provides access to additional controller capacity.
Its available action depends on whether your account already has an unused controller slot.
When No Additional Controller Slot Is Available
The card displays Purchase.
Selecting this option allows you to obtain an Additional Domain subscription.
An Additional Domain is an additional controller license that lets you connect and manage another website.
Additional Domain subscriptions are available to customers on the Pro and Agency plans.
Each Additional Domain includes the same features and resource allowances as the Pro plan.
You can review the relevant subscriptions here:
When an Additional Controller Slot Is Available
If your account already has an unused controller slot, the card displays an action to create a new controller instead of purchasing another license.
This can occur when:
- You have purchased an Additional Domain subscription but have not yet created its controller.
- Your Agency subscription includes available controller capacity.
Select the creation action to begin registering another website.
The new website receives its own controller and unique Controller ID.
How Many Additional Domains Can I Have?
There is currently no fixed maximum number of Additional Domain subscriptions.
Eligible accounts can expand from a small number of websites to much larger portfolios.
Each additional controller is managed individually, with its own configuration and applicable resource allowances.
The number of included controllers depends on your subscription. Additional capacity beyond the included controllers requires the appropriate subscription.
6. Understanding the Main Controller
The first controller created for your account is your main controller.
It always appears first in the controller list.
Unlike additional controllers, the main controller cannot be deleted.
This distinction is important when managing a multi-website account.
| Controller type | Can be configured? | Can be deleted? |
|---|---|---|
| Main controller | Yes | No |
| Additional controller | Yes | Yes |
The main controller can still be managed through its available settings and actions, including domain configuration where permitted.
If you need to use the main controller for a different domain, consider the available domain-change option rather than attempting to remove it.
7. Deleting an Additional Controller
If an additional controller is no longer needed, you can remove it using its context menu.
- Open the Controllers Overview.
- Locate the additional controller you want to remove.
- Open its three-dot menu.
- Select Delete Controller.
- Follow the confirmation process.
The Delete Controller action is available only for eligible additional controllers.
Important: Removing a controller is different from changing its domain or managing an Additional Domain subscription.
Before deleting a controller, confirm that you no longer need its website configuration and associated information.
Do not assume that deleting a controller automatically cancels its associated subscription.
8. Managing Multiple Websites Efficiently
If you manage several websites, the Controllers page provides a convenient starting point for routine administration.
A useful workflow is:
- Review your controllers: Confirm that the registered domains are correct.
- Check overall usage: Identify whether your portfolio is approaching its combined resource allowances.
- Check individual usage: Look for controllers with unusually high API or job consumption.
- Verify configuration: Make sure each website has the intended domain and sitemap.
- Assign technical contacts: Configure developer email addresses where appropriate.
- Open the relevant workspace: Switch to a controller's Dashboard or Site Workspace when you need to investigate accessibility results.
This approach is especially useful for agencies and organizations responsible for multiple websites.
Although your controllers share one account, each website retains its individual settings and accessibility data.
9. Frequently Asked Questions
What is a controller?
A controller represents a website registered with SimplifyAccess. It maintains the website's configuration, accessibility information, and applicable resource usage.
Can I manage several websites from one account?
Yes. Pro and Agency customers can obtain additional controller capacity, while Agency subscriptions include multiple controllers.
What is an Additional Domain?
An Additional Domain is an additional controller license for another website. It includes the same features and resource limits as the Pro plan.
Is there a maximum number of Additional Domains?
There is currently no fixed maximum number of additional domains that an eligible account can subscribe to.
Why does the Buy an additional Domain card show different buttons?
The action depends on your available controller capacity.
If no unused additional controller slot exists, the card offers a purchase action.
If an unused slot is available, it offers the option to create a new controller.
Can I delete my main controller?
No. The first controller is the main controller and cannot be deleted.
Can I change the domain of an existing controller?
Yes, subject to the available domain-change allowance and applicable configuration requirements.
Do I need to enter a sitemap?
The default sitemap path is based on your registered domain and /sitemap.xml. If your website uses a different location, you can configure it in the controller settings.
What happens if I leave the developer email empty?
SimplifyAccess uses your account email address for the relevant accessibility-related messages.
Does each controller have separate usage limits?
Yes. Most resource allowances apply individually to each controller. Support tickets are shared at account level.
Does deleting a controller cancel its subscription?
Controller deletion and subscription management are separate operations. Do not assume that removing a controller automatically cancels an Additional Domain subscription.
One account, multiple websites: Controllers make it possible to manage website accessibility individually while maintaining a clear overview of your domains, configurations, and resource consumption.