Appian Community and Appian Academy are being upgraded. As a part of the upgrade, Appian Community is currently in read-only mode, and user registration is disabled until August 3. We apologize for any inconvenience this may cause, but a more secure, stable, and performant Community experience is coming soon!
The new Appian Community launches August 3, followed by Appian Academy on August 7. During the migration, Appian Community Edition, Appian Academy, Documentation, Certifications, Instructor-led Customer Training, Partner Sales Training & Accreditation, and Forum (for Appian Partners and Customers only) will remain available.
I want to check if we have any workaround if we have the bot-wise-credentials configuration, instead of using a common ID for all bots? like each bot uses different creds to login for that robotic task ?
Discussion posts and replies are publicly visible
Can you explain further your specific use case? Just to understand what's the goal you are trying to address. Thanks.
Sure, let's assume we have 2 creds(cred 1 and cred 2) for a portal to login into through appian rpa and we have 2 instances running one is picked by bot 1 and another by bot2 so I would like to know if it's possible that rpa bot1 uses cred 1 and bot 2 uses cred 2 to login into that portal. In case we have a portal limitation that at one time only 1 cred can be used and if another bot tries to login with same cred it logs out of the previous session or does not let us login.
Easiest pattern I’ve seen is to handle creds outside the bots, then inject them when the job spins up. A vault plus some mapping logic usually works better than trying to wire Appian to every single account manually. That’s kind of how I approached mayorsmanor.com/2025/04/how-many-periods-in-hockey-explanations-from-experts/ in a dashboard: external data source, internal routing. Keeps the robot definitions cleaner and easier to maintain.