I've been implementing Sprinto for a client over the last quarter. The bulk edit function for controls was a critical feature for mapping their extensive policy library efficiently.
As of this morning, that option appears to be gone from the control management interface. I've confirmed it's not a permissions issue. This is a significant operational setback. Manually editing hundreds of controls one-by-one is not a viable workflow for any organization of scale.
If this is a permanent change and not a temporary bug, it fundamentally alters the platform's utility for initial setup and ongoing maintenance. It increases implementation time and cost dramatically. I need to know if this is intentional, as it would require a major re-evaluation of the platform for my current and future engagements.
Has anyone else encountered this or received communication from their success manager?
Trust but verify — especially the fine print.
Welcome to the club of rude surprises, where features vanish overnight and the first notice is your own panic. I've seen this movie with other platforms, and it usually means one of two things.
Either it's a regression they'll sheepishly roll back after enough tickets, or it's a 'streamlining' decision made by a product team that doesn't have to live with the consequences. You're right to be alarmed. That kind of manual overhead doesn't just add time, it introduces errors and kills team morale during a critical phase. Before you re-evaluate the entire platform, have you checked if the bulk action is now hidden behind a new UI pattern, like a checkbox selector on a list view instead of a main menu button? Sometimes they 'improve' things into obscurity.
If it's truly gone, your next call shouldn't be to the community, it should be to your account manager with a very specific question: ask for the new documented, supported method for performing bulk updates on control attributes, and the estimated time for that operation on 500 records. Their answer, or lack thereof, will tell you everything.
Test the migration.
Your 'streamlining' theory is spot on. These decisions often come from a product manager chasing a shiny new metric, like 'simplified user journey,' with zero understanding of the operational tax it imposes.
But I'd push back slightly on the account manager move. In my experience, they'll just feed you placating corporate-speak and open a meaningless ticket. The real signal is in the support docs. If they've silently removed a major feature, the official documentation will either be silently edited or will now describe a comically manual process.
Check the Wayback Machine for last week's version of their control management guide. If bulk edit is gone from the docs, you have your answer: it's intentional and they're hoping no one kicks up a fuss until the next contract renewal.
-- cost first