Single sign-on centralises staff login, while parking administration roles and vehicle entitlements still need their own rules and review.
Single sign-on should cover the staff who need application access, the identity protocol and the roles they receive. A useful demonstration includes removed accounts, changed permissions and existing sessions, alongside a successful login and controlled emergency access.
Parking entitlement needs a separate conversation. Being recognised as an employee by the login service does not establish that their vehicle may use a particular zone today.
Single sign-on grew out of the need to replace separate application passwords with a shared identity service. In a federated arrangement, that service supplies an authentication assertion to the application. This centralises the login relationship, but application permissions still need their own rules.
It also says nothing by itself about a vehicle's parking entitlement. Internal administrators, tenants and visitors may have different identity arrangements, and their accounts should not acquire the same powers simply because they use a shared sign-in screen.
SSO is useful when IT needs a consistent way to manage staff accounts across applications. A small team may be adequately served by separate administration. If the aim is employee vehicle access, a permit process or entitlement feed is still needed; a login service cannot supply that policy by itself.
This distinction also makes support clearer. The team responsible for office identities may not be the team approving vehicle access, permit dates or parking administration roles.
Treat identity protocol, role mapping and account provisioning as separate parts of the proposal. Test someone whose login remains valid after their parking administration role is removed. Existing sessions need examination too, because a changed account and an already open session are different states.
A contractor might retain office access to finish work after a weekend vehicle permit expires. Copying every login entitlement into parking permissions would confuse those approval periods. Each needs an accountable administrator and a clear effective date.
Support arrangements should distinguish a failed login from a stale vehicle entitlement. If the identity provider is unavailable, emergency administrative access needs an approved route with controlled use and a record of activity.
Aero Ranger CORE documents actions governed by permissions and audit history, which are relevant to examining administrative changes after login.
Its public pages do not confirm a particular SSO provider or provisioning protocol. The supported configuration needs demonstration, including staff roles and the separate updates to parking entitlements.
Sources were reviewed on the publication date. Check the linked material for current details.
