Kurt Vollmerhause (QUT)
My feedback
6 results found
-
67 votes
Kurt Vollmerhause (QUT)
supported this idea
·
An error occurred while saving the comment -
47 votes
An error occurred while saving the comment
Kurt Vollmerhause (QUT)
commented
Supported. The institutional delete user policy should be applied consistently, regardless of the method used for removal. There are often use cases in which it is inefficient to deploy the Purge Users job for only a single identified user record, or a small number of records, which might better be deleted manually. An example for our institution is the annual purge process for community cohorts such as alumni, which (from Analytics reporting) may well produce only a few candidates for removal.
Kurt Vollmerhause (QUT)
supported this idea
·
-
33 votes
Kurt Vollmerhause (QUT)
supported this idea
·
An error occurred while saving the comment
Kurt Vollmerhause (QUT)
commented
This would be a useful enhancement, especially when the sandbox (whether standard or premium) is being used extensively for testing prior to implementation of a new service/product in the production environment.
-
76 votes
Kurt Vollmerhause (QUT)
supported this idea
·
An error occurred while saving the comment
Kurt Vollmerhause (QUT)
commented
Supported, this is a key requirement.
-
19 votes
Kurt Vollmerhause (QUT)
supported this idea
·
-
47 votes
Thank you again for sharing your idea and for the thoughtful input you've provided. When we first discussed it, I was optimistic about exploring it further,
While I had hoped to prioritize this enhancement, it hasn’t gained the traction we typically look for to move forward. As a result, it’s unlikely to be implemented in the foreseeable future. That said, your feedback remains valuable, and I’ll continue to keep it in mind as our roadmap evolves.
Kurt Vollmerhause (QUT)
supported this idea
·
Agreed, this would provide Admins greater transparency and control over granular user permissions in Alma.