Talis Aspire Reading Lists
Welcome to Talis Aspire Ideas Forum.
5 results found
-
Allow the default invite text and subject line to be set at tenancy level
At the moment the default email invite text and subject line are fixed - on completion of this story, they will be configurable at tenancy level.
9 votes -
Allow users to request roles rather than waiting to be invited
At the moment an academic has to wait to receive an invite to edit a list from a system administrator. Academics who are proactive and have discovered the system have no way of gaining an entry point.
On completion of this story they would proactively be able to request various roles. The request is added to a queue and at some future point an administrator can approve or deny the request.
7 votes -
Allow invites scoped to multiple points in the hierarchy to be sent in one batch
At the moment an administrator must send a separate invite email for each list or module they would like a user to have permissions over.
On completion of this story administrators would be able to send one invite allowing users the same permission over multiple lists or modules.
5 votesUser management is not in our near term development focus so it has been moved to the longer term backlog.
Ideas may be graduated from the backlog as we get through the ones that are planned.
-
Allow invites to be created without sending emails
At the moment an email invite is sent for every invite issued - even if the user is already has an active login to Aspire. This can result in multiple emails sitting in a user's inbox.
Rather than emailing invites to users, administrators can elect to suppress the email invites.
In this circumstance, users are asked to accept invites the next time they log into the system.
3 votesThis is not currently in our near term development focus so it has been moved to the longer term backlog while we focus on items in the development focus.
Ideas may be graduated from the backlog as we get through the ones that are planned.
-
Node level "List creator" role
We would like to give list creator roles at a node or department level. At the moment, it is only available at tenancy level. We would like to limit users' ability to create lists anywhere, but allow them to create them as necessary in their department's area.
1 voteWe are not going to focus on this right now but we do plan to visit this as part of a wider look at how we manage scoping and hierarchy
- Don't see your idea?