You should be able to handle this type of URI using the Regular Expression option for the UR Match Detection method, and setting the regex string to something like the following:
^https:\/\/([a-z0-9-]+)\.account\.gic\.gc\.ca\/(.*)
The above should match any URL that starts with https://, followed by an alphanumeric string that optionally contains the hyphen (-) character, followed by the string .account.gic.gc.ca/, followed by a character string of arbitrary length (including 0). You may need to experiment with this to get it right.
Your other concerns seem like they would be solvable using some method of prioritizing the matching logins. There are several existing feature requests that propose this type of functionality:
- Set priorities for auto fill when multiple log ins available
- When listing credentials for a site, any that are favorited should be at the top of the list
- Better support for multiple logins on the same site - add favourite flag/priority-value to credentials
- Browser plugin - entries sorted alphabetically not by last usage
In the meantime, if your children’s accounts are only used very rarely, you could set the URI Match Detection method to Never for all URIs in their accounts. On those occasions that you need a child’s credentials, you can search for that login item, then select the relevant account from the search results to view it, and click the Auto-fill button that is available below the item’s information (this forces the login information to be auto-filled, even if there is no URI match).