To create an access account, select it as the option in the Accounts > Add menu (for details see: Add - Access account) .
The access account will access resources like any other account except for the location restriction. It's only really necessary though if you are offering resources that don't use IP as the authorisation method.
If you are using local authentication
If your site uses local accounts - i.e. you have connected OpenAthens to your own directory for authentications - then access accounts are still likely to be the best solutions for walk-in users as each ID your systems pass to us must represent an individual... and it is often the case that sites do not want to create those records for walk-in users anyway. The practicalities of the access accounts in use are:
- Enable the function that presents users with the option to sign in with either type of account
- This will display the option to all users at least once - the user's choice is remembered so users should only see it once on their personal devices
- If regular users and walk-in users access the same terminals, the choices of one group may impact the experience of the other group depending on how your terminals handle cookies
- You will have to remove the default flag from your connection
- Ensure the walk-in users sign into OpenAthens before they try to access any content
- This can be as simple as sending them to MyAthens (https://my.openathens.net)
Some federations do not permit shared accounts and require that all users be uniquely identifiable (e.g. UK Access Management federation). Access accounts will not work for organisation / resource combinations within those federations where we know these restrictions exist.