The Site Details button allows the general details of the site to be changed after it has been created. The site must be in Installer Mode for the site details to be changed.

To modify the Site Details:

1. Click the Site Details button.

   The Site Details lightbox displays.

2. Change the details as required, such as the Name, Timezone, Country and Address of the site.

   Note: For a timezone change to take effect on the Controller, you must publish the configuration.

3. Change the Subscription and Guarding details as required.

   Note: These are not applicable for Demo Sites.

4. Click the OK button.

   The site details are changed.

The Site Notes button opens the notes for the site, where you can add, edit, and delete notes for you and other Technicians to refer to.

Creating a Site Note

1. Click the Site Notes button.

   The Notes lightbox displays.

2. Click the + button to create a new note.

3. Type out the note you would like to add for this site. Each note is limited to 500 characters.

4. Click the SAVE button.

   The note is added to the left-hand navigation panel within the Notes lightbox. Notes are listed in this panel in order of most recently modified.

5. Click the x button to close the Notes lightbox.

Editing a Site Note

1. Click the Site Notes button.

   The Notes lightbox displays.

2. Select the note from the left-hand navigation panel.

3. Type in the text area to make any required changes.

4. Click SAVE, then click the x button to close the Notes lightbox.

Deleting a Site Note

1. Click the Site Notes button.

   1. The Notes lightbox displays.

2. Select the note from the left-hand navigation panel, and click the DELETE button.

3. Click YES, then click the x button to close the Notes lightbox.

The 'SITE ACTIONS' section of a site in the Installer Portal contains key actions around the configuration and activation of the site. The available options depend on the current state of the site, but can include:

At all times:

• View the Site Details

• View, add, and modify Site Notes

• View and change the Key Account Holder

Only before the site is activated:

• Activate the site (see Activation)

Only once the site is activated:

• Download the Monitoring Report (see Alarm transmitters or IP Alarms)

Only in Installer Mode (or before the site is activated):

• Modify the Site Details

• Create, move or delete site from Credential Groups

• Edit Credentials (User Code Length, Enable Tags)

• Enable Test Mode (cannot be done manually before activation)

• Invite yourself to the site

• Publish configuration to the Controller

The following actions can be performed before a site been added to a :

Add to New Group:

A site can be added to a Credential Group during the initial configuration or once a site is activated.

1. Click the Credentials dropdown menu.

2. Select Add to New Group. The Add to New Group lightbox displays.

3. Enter the Name of the Credential Group.

4. Click NEXT.

5. A confirmation warning will appear. To add the site to the new Credential Group, click OK.

Add to Existing Group:

A site can be added to a Credential Group during the initial configuration or once a site is activated.

1. Click the Credentials dropdown menu.

2. Select Add to Existing Group. The Add to New Group lightbox displays.

3. Select the Credential Group from the drop-down menu and click NEXT.

4. A confirmation warning will appear. To add the site to the new Credential Group, click OK.

WARNING: If you add an activated site to a credential group, all of the site's credentials will be removed and the site will inherit the credentials of the group you are adding it to.

Edit Credential Group:

This action can also be performed by clicking on the Credential Groups if is it visible on the SITES tab in the Installer Portal.

1. Click the Credentials dropdown menu.

2. Select Edit Credentials. The Edit Credential Group lightbox displays.

3. The following configuration can be changed from this lightbox.

   • Credential Group Name

   • Length of the User Code – this will change the length of user codes generated for all sites within the Credential Group. See Setting the User Code Length.

   • Enable/disable the use of Tags for all sites within the Credential Group

Setting the User Code length

You can set the length that User Codes will be when they are generated for users in the SMB app. User codes that have already been assigned to users will not be affected if you change the minimum user code length.

Note that this option only displays if at least one T30 Terminal has been configured for the site. The User Code Length can only be changed before the site has been activated or while in Installer Mode.

To set the minimum User Code length:

1. If the site has been activated, ask the customer to enable Installer Mode.

2. Click the User Code Length button.

   The User Code Length lightbox displays.

3. Select the Minimum length from the drop-down list. Generally, longer User Codes are considered more secure.

4. Click the OK button. New User Codes will now be generated at this length in the SMB app.

NOTE:

• 4 - "Not recommended for sites using more than 100 user codes"

• 5 - "Not recommended for sites using more than 1,000 user codes"

• 6 to 8 - "Recommended level of security for most sites"

Tags

The Tags toggle defines whether Key Tag assignment and management functionality is enabled for the site's Credential Group.

Tags are considered a single-factor credential. If tags are used for access, the area the doors are associated with must be configured to disarm with a single-factor authentication. This is part of the Area configuration.

The Key Account Holder button lets Install Managers view the details of the Key Account Holder and also change the Key Account Holder.

Note: Install Technicians cannot change the Key Account Holder. For more about Technician roles, refer to Installer Portal overview > 'TECHNICIANS tab'.

1. Click the Key Account Holder button.

   The Key Account Holder lightbox displays.

2. Click the CHANGE KEY ACCOUNT HOLDER button.

   The New Key Account Holder lightbox displays.

3. Enter the email address of an existing SMB app user for this site.

4. Click OK.

5. In the confirmation pop-up, tick the check box then click OK.

   The selected user is given the Site Manager role and is made the Key Account Holder. They will receive an email informing them of the change.

The following actions can be performed after a site has been added to a Credential Group:

Remove from Group:

This option only displays if a site is already in a Credential Group.

1. Click the Credentials dropdown menu.

2. Select Remove from Group. The Remove from Group lightbox displays.

3. A confirmation warning will appear. To remove the site from the Credential Group, click OK.

WARNING: Removing this site from its current credential group will deactivate the site credentials.

Move to Existing Group:

This option only displays if a site is already in a Credential Group.

1. Click the Credentials dropdown menu.

2. Select Move to Existing Group. The Move to New Group lightbox displays.

3. Select the Credential Group from the drop-down menu and click NEXT.

4. A confirmation warning will appear. To remove the site from the Credential Group, click OK.

WARNING: If you add an activated site to a credential group, all of the site's credentials will be removed and the site will inherit the credentials of the group you are adding it to.

What are Credential Groups?

A Credential Group is a group of sites that allows users within the group to have a single credential for all sites they have privileges for.

Credential Group functionality is applied to user code and key tag credentials.

• Generate one user code for a user to use across all sites within the Credential Group.

• Key tags only need to be scanned and allocated once for a user to use across all sites within the Credential Group.

Example:

There are two sites in a Credential Group – Site A and Site B.

A user code generated on Site A will work on Site B if the user is granted privileges to that site. No new user code is needed for Site B.

Notes:

• At least one site in the Credential Group must be in Installer Mode for changes to be made to the Credential Group.

• All Technician types can add sites to Credential Groups or edit credentials.

• Only Organisation Managers, Branch Managers and Installer Managers can move sites between Credential Groups using the 'Move to Existing Group' option or remove sites from a group.

The Credentials button allows for managing Credential Groups, user code length, and enabling tags.

Before a site is added to a Credential Group, the following actions are available:

• Add to New Group

• Add to Existing Group

• Edit Credentials

Once a site is added to a Credential Group, the following actions are available:

• Remove from Group

• Move to Existing Group

• Edit Credentials

NOTE: Credential Group changes do not need to be PUBLISHED to take effect on a site.

When should I use a CG? When users travel to different sites that can be linked together and want to use the same credential. E.g. Retail Franchises or Quick Service Restaurants where workers can work at multiple locations - they will only have to remember one user code.

What does it mean to add sites into a CG? A user's credentials will be shared on all sites in the same Credential Group, meaning a user does not have to scan their tag or generate a user code for each individual site.

Can I add a site to more than one CG? No, a site can only be assigned to one Credential Group.

Who can make changes to a CG? Organisation Managers, Branch Managers and Installer Managers can move sites between groups using the 'Move to Existing Group' option or remove sites from a group. All Technician types can add sites to groups or edit credentials.

Does the Site need to be in Installer Mode to make changes? At least one site in the Credential Group must be in Installer Mode for changes to be made.

Do I need to PUBLISH changes to CG? No, changes will be applied as soon as they are saved.

How long before tags/user codes can be used after I added my site to the CG? Provided the network connection is stable, a site's tags and user codes can immediately be used at all sites in the Credential Group.

How do I know what sites are in a Credential Group? In the Installer Portal, select COLUMNS and choose 'Credential Group'.

What if the customer doesn't want a site in a CG anymore?

1. Select Remove from Group

The Remove from Group lightbox displays

1. A confirmation warning will appear. To remove the site from the Credential Group, click OK.

WARNING: Removing this site from its current credential group will deactivate all site credentials. The site will then become a standalone site who can regenerate its own credentials.

Can I add a Demo Site to a CG? No, demo sites are intended for training and practicing configuration.

Will anything change in the SMB app that Customers use? Yes, Site Managers can now see Credential Group(s) on their Credentials Page, if they are privileged in any CG(s). Site Managers can now generate tag/user code credentials once for a user to access all sites in their CG.

Changes made within the Installer Portal do not take effect until they are published to the Controller with the PUBLISH or REFRESH button. The PUBLISH button displays when there are pending hardware changes; the REFRESH button displays at all other times to allow you to ensure the Controller configuration is up to date (e.g. if you have made a non-hardware site change).

When publishing/refreshing configuration to the Controller, doors will revert to their original schedule regardless of whether the customer has performed an override. For example, if the customer has overridden the schedule to Free, and then a Lock Door override is performed, the door will lock and the override will be lost.

Once changes have been published to the Controller, there is no way to restore to a previously published version. To revert the site configuration to how it was when it was last published, select DISMISS CHANGES under Unpublished Changes.

Note: Configuration can only be published/refreshed when the Controller is online.

Publishing configuration to the Controller

1. All changes appear in the sidebar to the right under Unpublished Changes.

   Note: If no changes have been made since the last publish, the 'Unpublished Changes' section does not display.

2. Select the floating PUBLISH button to publish the changes.

   Note: If the Controller is offline, the button will be disabled. If there are no pending hardware configuration changes, the 'REFRESH' button shows instead.

3. When PUBLISH is selected, a pop-up window will appear asking you to confirm you want the changes published. Select Publish Changes. Note: For all newly-installed sites, when the Controller comes online, it will immediately start downloading new firmware. If the firmware is still downloading when you attempt to publish the changes, a warning will appear. If changes are published while the download is not completed, the download will restart from the beginning.

4. After the configuration has been published, a small confirmation displays.

Refreshing the Controller configuration

If you have not made any hardware changes, but need to update the Controller's configuration anyway (e.g. you changed the site's timezone), you can use the 'REFRESH' button.

1. Select the floating REFRESH button to publish the current configuration to the Controller. Note: If the Controller is offline, the button will be disabled. If you have pending hardware configuration changes, the 'PUBLISH' button shows instead.

2. When REFRESH is selected, a pop-up window will appear asking you to confirm you want the Controller to be updated. Select Yes. Note: For all newly-installed sites, when the Controller comes online, it will immediately start downloading new firmware. If the firmware is still downloading when you attempt to refresh the configuration, a warning will appear. If configuration is refreshed while the download is not completed, the download will restart from the beginning.

3. After the configuration has been refreshed, a small confirmation displays.

The Display Names button lets Technicians change the names of an SMB site's roles, which are by default 'Site Manager', 'Site Admin', and 'Site Member'. An SMB customer may request this, for example, so that the role names in the app correspond with the job titles that they already use.

1. Click the Display Names button.

   The Display Names lightbox displays.

2. Change the Role Names as requested by the customer.

3. Click OK. Wherever a role type is displayed or selectable in the SMB app, the new role names will now be displayed.

If you wish to use the customer app to test the site's access, alarm, and app behaviour from the perspective of the customer, you can invite yourself to the site. This can only be done before the site has been activated or while in Installer Mode. As a Technician, you have some restrictions in the customer app. You cannot:

• see the details of any user (except for names in events)

• create, delete, or send invites to users

• close incidents

• manually call out a guard.

You can only invite yourself to sites where you are recorded as being a Technician of the customer's Installer. You can send as many invitations as you like. You can have just one credential per site per technician. If you invite yourself as a user to multiple sites, you can interact with readers at all of those sites and can switch between sites in the customer app.

Inviting yourself to the site

To request a credential for yourself to the customer's site:

1. If the site has been activated, ask the customer to enable Installer Mode.

2. Click the Invite Myself To The Site button.

   This sends an invitation to the email address entered against your Technician account; there is no option to send it to a different email address. SMS verification is not required.

3. Download the Gallagher SMB app if you have not already.

4. Select the Complete Registration link in the email invitation.

Test Mode allows Technicians to install, configure, and test an SMB site without annoying or alarming anyone by setting off the sirens or any other type of device activated in response to an alarm. Test mode also prevents Site Managers, guards, and monitoring services from responding to alarms generated while the system is being tested.

Test Mode can be used as part of your ongoing maintenance process. All Gallagher-manufactured parts are covered under the Gallagher SMB Product Warranty Policy. Annual testing and maintenance checks are recommended to ensure the solution is meeting the customer’s needs.

New sites

Test Mode starts automatically when a new site is created, and ends when the site is activated.

Test Mode gives Technicians the ability to test individual outputs. Alarm Relays are bypassed, and technicians can ‘chirp’ test outputs from this screen.

When Test Mode is enabled for new sites:

• All alarm outputs are automatically bypassed. This prevents sirens etc. being activated during Test Mode.

• The Installer Portal will display a banner showing when Test Mode will expire.

During Test Mode (new sites)

Technicians can "Test" individual outputs by using the TEST found next to the outputs in the Installer Portal. This will override the output to On for 1 second, then Bypass the alarm output again (or cancel the override) which will turn it off.

Existing sites

Enabling Test Mode for existing sites

1. Once a site is activated, ask the Site Manager to enable Installer Mode within the Gallagher SMB app. Notes:

   • Installer Mode allows Technicians to make configuration changes to the site in the Installer Portal and publish changes to the Controller.

   • Test Mode can only be enabled after Installer Mode has been enabled.

   • Test Mode puts the site in a state that is no longer production-ready (alarm relays will not activate), therefore Test Mode can only be enabled for a short period of time, less than 24 hours.

   • If Installer Mode is disabled, Test Mode will automatically be disabled too.

2. After Installer Mode is enabled in the Customer app, the Enable Test button is visible in the Installer Portal.

3. Select Enable Test Mode in the Admin section of the Installer Portal.

4. Select an expiry time.

   If the site has Monitoring or Guarding enabled, a message will display to remind the Technician to contact the Monitoring or Guarding company to advise that the system is being tested. This will prevent unnecessary call-outs.

   Note: Test Mode can only be enabled if there are no Guard call-outs currently in progress for the site.

When Test Mode is enabled:

• All alarm outputs are automatically bypassed. This prevents sirens etc. being activated during Test Mode.

• Any currently in-progress Incidents will not receive any new alarms (existing incidents remain open).

• A new Test Mode incident is created to capture any alarms generated during Test Mode.

• A notification is sent to all Site Managers alerting them that Test Mode is enabled.

• The Installer Portal will display a banner showing when Test Mode will expire.

• The Customer app will display a banner explaining that the site is under maintenance.

During Test Mode (existing sites)

• Any alarms generated will be added to the 'Test Mode Incident'.

• Technicians can "Test" individual outputs by using the TEST found next to the outputs in the Installer Portal.

  This will override the output to On for 1 second, then Bypass the alarm output again (or cancel the override) which will turn it off.

• If Monitoring is enabled during Test Mode, the Technician will be advised, when publishing the change, that the Monitoring company needs to be informed that the system is under test.

Disabling Test Mode (existing sites)

• Test Mode can be disabled due to any of the following occurring:

  The Technician selects Disable Test Mode in the Admin section of the Installer Portal.

  The Test Mode period expires.

  The site is taken out of Installer Mode (expires or is manually disabled).

• Ideally, a technician disables Test Mode manually by selecting Disable Test Mode in the Admin section of the Installer Portal when they have finished testing, as the site will be 'live' again when Test Mode is disabled.

• For sites with Monitoring or Guarding enabled, if Test Mode is disabled manually, a reminder will display to inform the Monitoring or Guarding company that testing has finished.

When Test Mode is disabled:

• Incidents generated during Test Mode are automatically closed.

• Alarm outputs are un-bypassed.

• Banners in both the Customer app and the Installer Portal are removed.