Submit an idea
The Ideas Space is the surface you give to the rest of the company: describe a painful task or an app idea in two minutes, and it lands in the backlog.
In the appIdeas Space
The Ideas Space is the surface you give to the rest of the company: describe a painful task or an app idea in two minutes, and it lands in the backlog.
The Ideas Space is a separate, deliberately small surface. It exists so anybody in the company can ask for software without being given the keys to build it.
Somebody with access to the workspace opens it from Application Portfolio › Open the submission space, and shares the link. From there the submitter never sees a project, a version or an agent.
What a submitter sees
Their own submissions, each with a status, the department it came from, when it was sent and how. Nothing else. A line at the bottom of the list says so plainly: You can only submit needs. Building applications stays with the teams cleared for it.
The account carries a Restricted account badge in the topbar, so it is never ambiguous which side of the wall you are on.
Two ways to describe a need
Submit an idea asks how you want to go about it. The result is identical on the review side, so it is purely a matter of what the person is comfortable with.
The form asks for a title, a description, what data the solution would need, whether it would involve artificial intelligence, and how often the need comes up. Nothing is mandatory beyond the basics: answer as best you can, someone will come back to you if needed.
After sending
The submission lands in the application-needs backlog with the status New, and the submitter is notified as it moves forward. See Collect what the business needs for what happens on the review side.
The assistant path is worth defaulting to when you roll this out to a department. People under-describe their own pain, and the questions are what turn "the export is annoying" into something a team can act on.