Hey nodirn! I had a similar system at the previous company I was with. It wasn't a perfect system, but it was useful and displayed some of the ad-hoc/non-standard things we could build with anaplan. Using two modules, and leveraging user controls (Roles > Modules), our design was: - Users create an item in a numbered list, - Users enter details into line items of module A (that was dimensionalized by that list) that they had Write access to, and - Users could view the status of their ticket in Module B (that referenced values entered in Module A...and had additional line items for Dev comments), which they only had Read access to. Module B was also dimensionalized by the numbered list. Development/COE/support team had Write access to module B, so they could update the ticket status, comments, etc. *as far as dashboards, Module A was published to a dashboard "Submit a Ticket" and Module B was published to "Review Ticket Status" It wasn't perfect, could technically be gamed by clever users to change their entries if they wanted - but we didn't have risk exposure, so we weren't worried about it. Answering your questions specifically: 1. The above took care of it for the most part. We didn't run operation risk if they managed to change the details of their ticket, so maybe above solution won't help your specific use case. 2. We were unable to do this - no native functionality that I am familiar with exists. We just had a line item for them to enter name/ID#. 3. May be able to manage a portion of this with a Process and MAILTO(), but we didn't look into it. Hope that helps!
... View more