Enable / Disable Seed Admin

The Seed Administrator setting controls whether WebReports automatically creates the initial administrator account when the application starts.

Use this article to enable or disable the SeedAdministrator setting in the WebReports appsettings.json file.

Before You Begin

Before editing the WebReports configuration:

• Make sure you have access to the WebReports installation directory.
• Make sure you have permission to edit appsettings.json.
• Create a backup copy of appsettings.json before making changes.

Use caution when editing appsettings.json. Incorrect formatting can prevent WebReports from loading correctly.

Open appsettings.json

1. Navigate to the WebReports installation directory.
2. Locate appsettings.json.
3. Open the file in a text editor with the appropriate permissions.
4. Locate the SeedAdministrator setting.

SeedAdministrator setting in appsettings.json

Enable Seed Administrator

To enable Seed Administrator, set the value to:

"SeedAdministrator": true

When enabled, WebReports can seed the administrator account during application startup.

Disable Seed Administrator

To disable Seed Administrator, set the value to:

"SeedAdministrator": false

When disabled, WebReports will not seed the administrator account through this setting.

Save the Configuration

1. Save the changes to appsettings.json.
2. Close the text editor.
3. Confirm that the SeedAdministrator value is set correctly.

If the change does not appear to take effect, restart the WebReports application or contact BridgeWorks Support for assistance.

Troubleshooting

WebReports Does Not Start After Editing appsettings.json

• Reopen appsettings.json.
• Confirm that the JSON formatting is still valid.
• Confirm that the SeedAdministrator value is either true or false.
• Restore the backup copy if necessary.

Seed Administrator Does Not Behave as Expected

• Confirm that you edited the correct WebReports appsettings.json file.
• Verify that the value was saved successfully.
• Confirm that there are no duplicate SeedAdministrator entries in the configuration file.

If the issue continues, contact BridgeWorks Support.

Related Articles

• Installing WebReports on Windows
• Configuring WebReports SQL Server Using SSMS
• WebReports Deployment Requirements and Network Architecture