Just tried the Delinea mobile app for the first time. Wanted to check on a server permission while away from my desk. Honestly, it felt impossible to do anything useful.
The menu is confusing, and I couldn't find basic functions our ops team needs daily. Is it just me? I really like the desktop platform for PAM, but this feels like an afterthought. How do other teams handle urgent access requests on the go? 😕
It's not just you. That mobile app is a glorified notification bell. Tried to approve a simple request on it last month and ended up having to call a colleague to log in on a laptop for me.
You hit the nail on the head: it's a complete afterthought. Feels like their dev team built it in a weekend to check a box on a features list.
For urgent stuff? We gave up and use a secure remote desktop app to hit the web portal. Clunky, but at least it works.
been there, migrated that
Right? The notification bell comparison is perfect. I get alerts, but then I can't actually *do* the thing it's alerting me about half the time.
Your remote desktop workaround is smart. We tried that but our security policy blocks it. So we're stuck with a clunky approval process via email for anything urgent, which defeats the whole purpose of having a mobile app.
Trial first, ask later.
You're definitely not alone on this. I've had similar frustrations trying to check permissions from my phone. The layout just doesn't map to how you actually work in the desktop console.
For urgent access, we set up a simple Zapier automation. It catches approval request emails and sends a formatted SMS with approve/deny links back to the web portal. It's not perfect, but it gets the job done without needing the official app.
Yeah, the email fallback really does defeat the purpose, doesn't it? You end up with two broken systems instead of one functional one.
Your point about the security policy blocking the remote desktop workaround is a huge, practical roadblock that gets overlooked. It highlights how a bad mobile experience can actually force teams into less secure practices, which is ironic for a PAM tool.
That Zapier SMS idea someone mentioned is clever, but it shouldn't be on us to build these duct-tape solutions.
Totally agree about the forced less-secure practices being the ironic part. It creates this weird pressure where you're balancing policy against actually getting work done.
That Zapier SMS workaround is clever, but you're right - we shouldn't need a side project just to make a core feature functional. It feels like the mobile app was built for a checklist, not for the real-world "I'm away from my desk" scenario it's meant to solve.
Makes me wonder if the product managers ever have to use it themselves during an actual on-call rotation.
null
>Feels like their dev team built it in a weekend to check a box on a features list.
I bet that's exactly what happened. I'm still learning PAM tools, but I see this all the time in other apps. Someone high up says "we need a mobile app," so they ship the bare minimum.
Your remote desktop workaround is interesting. What app do you use for that? I'm trying to picture the setup. Does the web portal even work well on a phone screen? Seems like it'd be a pinch-and-zoom nightmare.
Containers are magic, but I want to know how the magic works.
Your desktop experience is likely the same. The menus on the core platform are a maze too. You just get lost faster on a small screen.
The "afterthought" feeling is classic. Their product checklist had "mobile app" but not "useful mobile app". They got the checkbox.
You'll notice they never demo the mobile part at sales calls. Wonder why.
Your stack is too complicated.
That email fallback loop is the worst part. It's not just clunky, it creates an audit trail nightmare. Suddenly you're tracking approvals across email threads, the main platform, and maybe a Slack channel.
I actually think it gets worse than just not being able to act. Sometimes I tap the notification, the app opens, and then I get a generic error. So now I don't even know *what* I was supposed to approve or deny. The app functionally makes me *less* informed than if I'd just gotten a plain text alert.
Have you run into that specific error-on-open problem, or is our instance just uniquely cursed?
Happy testing!
Right? I had the exact same first impression. It's like they ported the desktop navigation without considering that you can't hover over tiny nested menu items on a phone screen.
What really got me was trying to use the search function from the mobile app to find a specific server. On desktop, it's a core workflow. On mobile, the search results were laggy and truncated key info like the server's environment tag, which is critical for our ops checks.
For urgent access, our team has a shared "on-call laptop" with a cellular hotspot as a last resort. It's overkill, but it's the only reliable way to use the actual web portal when you're truly mobile. Kind of sad when a dedicated app creates more friction than carrying extra hardware.
Automate all the things.
The search issue you described is exactly what I run into. On a desktop, missing a tag is annoying. On a mobile during an incident, it's a blocker. That lag makes you second-guess the results, which defeats the whole point of a quick check.
I'm curious, since you've tried both the broken app and the "on-call laptop" workaround, which one actually ends up being faster in a real pinch? Carrying extra hardware seems like it would add its own delay.
It also makes me wonder how this compares to something like CyberArk's mobile experience, or even a simpler tool like Keeper. Has anyone on your team used those for comparison?
You're right, it absolutely feels like an afterthought. I've done a few informal usability comparisons with other PAM mobile interfaces, and the Delinea app consistently scores lowest on task completion for basic ops functions like checking permissions.
What's telling is that the confusion often stems from a direct, unmodified port of the desktop interface's information architecture. On a large screen, you have the spatial context for nested menus. On mobile, that hierarchy collapses into a frustrating series of taps with no clear breadcrumbs. The "basic functions" you couldn't find are likely buried under a menu labeled something obtuse, which made perfect sense to the desktop UX designer.
Your question about handling urgent access on the go is the core of the failure. A functional mobile app should make that *easier*, not impossible. The fact that teams resort to Zapier automations or dedicated hardware, as others have mentioned, is a damning indictment of the app's design priorities. It shifts the security burden onto the user.
It's definitely not just you. I've watched our ops team struggle with that exact "check a permission" task, and it's painful. They end up just calling someone who's at a desk.
The core issue is they didn't design for the mobile context. On desktop, checking a permission is a multi-step navigation path that works. On mobile, you need a single, focused action. The menu confusion comes from squeezing a desktop IA onto a small screen without rethinking the user's goal.
It's a classic case of building the *same* product instead of the *right* product for the platform. Frustrating for a tool where quick access is the whole point 😕
Exactly this. That "single, focused action" point is so key. On desktop, you're in triage mode, you have time for steps. On mobile, you're usually reacting to an alert or a frantic message from someone else.
I've seen teams try to pre-build bookmarks for specific permission views on their phones, but it's a band-aid. It creates a whole separate maintenance task and still doesn't solve the notification-to-action loop.
The irony is, in trying to give us the "full" desktop experience, they ended up creating a tool that delivers none of the desktop's utility and all of its complexity.
Happy testing!