Have workspace name auto-populate based on user permissions and/or last-viewed workspace (Ideas Portal)

What is the challenge?

When a user submits an idea through the Ideas Portal, they have to manually pick the workspace from a dropdown every time, even if they only have access to one or two workspaces, or were just working in the one the idea belongs to. In organizations with many workspaces, the list is long and the names are often similar or internal-facing, so users pick the wrong one or leave it at the default. Ideas then land in the wrong backlog, and admins and product managers have to find and move them by hand. This adds friction for submitters and makes routing inconsistent for the teams that review ideas.

What is the impact?

Misrouted ideas slow down triage, because product owners don't see relevant ideas until someone reassigns them, and some ideas get overlooked entirely. Admins spend recurring time cleaning up workspace assignments instead of higher-value work. For submitters, the extra step and uncertainty ("which workspace is mine?") discourage participation, which reduces the volume and quality of feedback the portal is meant to capture. Over time, this weakens trust that ideas are reaching the right people, and it weakens reporting on idea volume and trends by workspace.

Describe your idea.

Pre-populate the workspace field on the idea submission form using context Aha! already has about the user:

1. Permission-based default: If the user only has access to one workspace (or the portal is scoped to one), auto-select it and optionally hide or lock the field.

2. Last-viewed workspace: If the user has access to several workspaces, default to the one they viewed most recently in Aha! Roadmaps, or the one they last submitted an idea to in the portal.

3. Filtered list: Limit the dropdown to workspaces the user actually has permission to see or submit to, rather than every workspace on the portal.

4. Admin controls: Let portal admins turn each behavior on or off, choose the order of precedence (e.g., permissions first, then last viewed, then a portal default), and decide whether users can override the pre-filled value.

The field would stay editable by default, so users can still change it when needed. This would cut submission steps, improve routing accuracy, and reduce admin cleanup, while keeping flexibility for users who contribute across multiple workspaces.