v1.0.96-beta
Last updated
Last updated
Release Date: 03.05.24
Profile Settings
In our upcoming update, we're enhancing the People tab in the console. Admins will gain more control over end-user preferences. Here's what's new:
Privacy Preferences: Set individual privacy settings within the admin console for a user and configure whether their schedule is hidden from other users, whether they are invite-able when scheduling, and who can schedule on behalf of the user.
Notification Settings: Set your notification preferences per protocol i.e. Teams, Emails, or Push notifications per user, for more personalisation of what alerts the user wants.
Schedule Settings: Establish fixed days for users, with options for repeating patterns, for when a user may be in with a team everyday one week, but 2 days with another team the week after.
Default Location/Team: Assign or change a user's default location or team, meaning when AIDRA forecasts this is the team they will be allocated with, or if they schedule, then these fields will be auto-populated for the user.
List of new features, including:
This is an early access release of the new gospace platform. As a result, not all functionality is available in this initial release, and some issues may arise. Certain modules are still in progress, but we've made this release available to enable thorough testing of your integrations and people settings.
Area | Feature | Functionality |
---|---|---|
List of functionality in progress visible within this release:
Locations - The Activation settings (starts/ends at) is available via the UI (user interface), however is not functioning entirely.
Location - Operating hours is available via the UI, however is not functioning entirely.
Integrations - On Occupancy integrations in this first release we are missing the first and last seen mapping fields, currently our system is auto-generating these via the integration.
People (Settings) - Fixed days is available via the UI, however is not populating the values.
People (Settings) - Notification preferences is currently in progress.
People (Settings) - Schedule managers within privacy preference is currently UI only, and any values set will not populate.
Connections - Connections are currently in progress, so you may encounter some errors.
Locations - Floorplan, and the modes in the top left are all in progress, and not representative of the final version.
Locations - Settings, the UI is functional, however any value set will not populate currently.
Locations - There may be some minor bugs in zones. For example, when editing a zone, the colour is overwritten; this is a known issue.
Notifications - People, there is an issue for some users with the toggles not being clickable, this will be fixed within the next couple days.
Privacy prefs - People, there is an issue for some users with the toggles not being clickable, this will be fixed within the next couple days, though, preferences will work if you click the list item, not the toggle.
Locations settings, teams settings and people settings are missing the changeset in the current user interface, so any changes made will not be applied until these are added.
Locations - On Add layer, the floorplan upload does not work in this release with the addition of changesets, this will be amended with the release of changesets.
Profile settings - Master user, currently you cannot set profile settings for a master user, this is being rectified currently.
Labels, we're working hard on bringing a labels v2, with further functionality, a better user experience, and fixing the current bugs associated to adding and removing labels to people or teams.
Note: This is a UAT environment where live feature developments are being continuously tested. You may experience temporary issues. Being a test environment please only use a dataset of up to 1000 records on Integrations
Teams
Further improvements to the teams tab resolving some existing bugs, and adding the ability to edit teams, and set properties of teams such as targets, headcount and more.
People
Ability to set default location of a user
Set the default location for a user, meaning when they go to schedule their location is pre-populated
People
Ability to set default team of a user
Set the default team for a user, meaning when they go to schedule their team is pre-populated
People
Ability to set fixed days and repeating patterns for a user
Set the days a user should be in the office, per location and create repeating patterns. For example set that the user is in Office A on Week 1, and Office B on Week 2, also set at an individual day level
People
Ability to turn off notifications per protocol for a user
Turn off/on email, push, or teams notifications for a user - what notifications they can receive is also populated by location settings
People
Ability to toggle whether a users schedule should be hidden from other users
Toggle where a users schedule can be shown to other users when they search for them, if off it will be hidden
People
Ability to toggle whether a user can be invited when a separate user is scheduling
Set whether a user can be invited by other users when they're scheduling space
People
Ability to toggle and set who can book on behalf of the user (issues known)
Configure who can book on behalf of the specified user, across anyone inf your division