Skip to Main Content
Nintex Ideas

👋 Use this site to provide feedback and ideas for all Nintex Products. See our post on Nintex Community "Welcome to Nintex Ideas" for more details on Nintex Ideas, how an idea is handled by our product teams and more!

If you have questions about Nintex Ideas, please contact

If you require support, please visit Nintex Customer Central

If you have a sales inquiry, please contact

Status Under Review
Categories General
Created by Guest
Created on Oct 21, 2019

Remove roles/responsiblities through user import functionality

The file upload of users that have changed their role, is adding their new role to their User profile, but is not removing the old roles.

With nearly 9000 users it is a huge administrative task to remove roles manually.

It would be great to be able to use the user import function as a true update of the users profile.
  • Attach files
  • Kerry Hiki
    Sep 7, 2022
    Thanks for the suggestion. We'll open this up for voting to gauge interest for now.

    However we could implement this as part of our role/user API plans coming up for next year.
  • Noala Degasperis
    Sep 7, 2022
    Whilst I can understand the reason for this suggestion, in my organisation we don't always want the existing role to be removed. If implemented I would want this to be a selectable option.

    Very frequently our staff move into another role for a short time only (eg a few weeks), and both their normal role and their new role are active in our HR system. In these cases the staff member will have two roles in Promapp (until they go back to their normal job) for the duration.

    If it's a permanent change of jobs then yes, we remove their existing assigned role. Temporary job changes are much more frequent than permanent job changes for us.

    If this suggestion is implemented I would require it to be an option so I can select whether to remove existing assigned roles.
  • Guest
    Sep 7, 2022
    I agree with this. I might also add a suggestion (which I was inclined to create a new one but instead will include it in here) is to have a unique ID associated with every Role/Responsibility.
    This way if we were to run an export we can make changes and import them back in to Promapp.
    The import will use whatever is in the file and overwrite the existing role based on the Unique ID.

    And if a Unique ID has a blank value upon import then this could be treated as a delete (with verification/merge options within Promapp after the import, especially if there are processes assigned to those roles)

    We are also fairly large and this is my current pain point since SSO Sync User Details does not sync role (or position title) information.

    In our organisation we have people moving between roles on a weekly basis (or at least their role title changes). I get a weekly report from our database and I have to manually change roles for each of these staff.

    Another use case which I've come across is that our organisation recently went through a change in how titles read. An example "Director (Financial Services)" became "Director, Financial Services".
    So in this case, I had to manually the records because I have imported the roles back when it was still in the old format.
    This is probably more of a once off scenario though.
  • Αγγελος Κουλουριδης
    Sep 7, 2022
    This must be added to the Product Development Roadmap ASAP !! How are you expecting your Customers to manage thousands of users MANUALLY?