<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Role-based chatbot implementation in Appian interfaces</title><link>https://community.appian.com/discussions/f/new-to-appian/40375/role-based-chatbot-implementation-in-appian-interfaces</link><description>Hi All, 
 I am working on an Expense Reimbursement System POC in Appian. 
 We have three different user roles: Employee, Manager, and Finance Team, each with separate interfaces. I need to implement an AI chatbot in all three interfaces that can answer</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Role-based chatbot implementation in Appian interfaces</title><link>https://community.appian.com/thread/154410?ContentTypeID=1</link><pubDate>Mon, 27 Apr 2026 12:10:48 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:b29ac2ff-3347-4489-a634-5b89139c6344</guid><dc:creator>Shubham Aware</dc:creator><description>&lt;p&gt;Use one reusable a!recordsChatField() with role-based record-level security on the Expense Claim Record Type and dynamic additionalInstructions per interface/role. No need for separate chatbot configurations unless each role needs completely different prompts or data sources.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Role-based chatbot implementation in Appian interfaces</title><link>https://community.appian.com/thread/154403?ContentTypeID=1</link><pubDate>Mon, 27 Apr 2026 04:45:21 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:ecd5ec5e-ca9d-41fd-90ef-8529847c51a8</guid><dc:creator>VarunTejaGurrapu</dc:creator><description>&lt;p&gt;Hi &lt;a href="/members/jananyi790908"&gt;jananyi790908&lt;/a&gt;&amp;nbsp;,&lt;br /&gt;&lt;br /&gt;as per your usecase, you can use a single record chat component and UI, and dynamically pass the inputs.&lt;br /&gt;&lt;br /&gt;I recommend to use record level security for the record type, ensures chatbot only givws output from which the loggedin user is a member of certain group.&lt;/p&gt;
&lt;p&gt;Yes, we can give dynamic context using - &lt;strong&gt;Additional Instructions, &lt;/strong&gt;parameter in the&lt;strong&gt; component configuration-&amp;gt;Behaviour.&lt;br /&gt;&lt;br /&gt;FYI - &lt;/strong&gt;Please check the relevant documentation -&amp;nbsp;&lt;a href="https://docs.appian.com/suite/help/26.3/Records_Chat_Component.html#security"&gt;docs.appian.com/.../Records_Chat_Component.html&lt;/a&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>