[Feature Request] Default landing page

[lonix1]

Is your feature request related to a problem? Please describe.
When I open portainer it shows the /home page by default. But I always immediately go to the /containers page.

Describe the solution you'd like
It would be nice to be able to set the "default" landing page. I would set it to the containers page.

Describe alternatives you've considered
None

Additional context
I'm sure it's different for different people in different environments. Maybe a sysadmin will always open the networks page as that is most relevant to him. Maybe an admin managing a cluster will always go to the stacks page. I'm mainly a dev, so I almost always go to the containers page to manage my apps. Having this as a configurable option will make many peoples' lives a tiny bit easier through better UX.

Thanks for considering it!

[jamescarppe]

Because you can have multiple environments set up within Portainer, we default to the "home" page list of environments so you can choose where to start. But we are looking at our UX in general and I'll pass this suggestion onto the team working on that.

[divStar]

I second this suggestion. Since I am running one environment, it'd be nice if I could at least auto-select it (as default) and thus be directly able to see its status, preferably even set the default landing Page to e.g. containers or custom stacks or whatever.

[outlookhazy]

Because you can have multiple environments set up within Portainer, we default to the "home" page list of environments so you can choose where to start.

Seems like the simplest solution would be to default to the Environment dashboard if there's only one available. At least that wouldn't require keeping track of any settings or adding the required UI elements. I can't think of a circumstance where someone with a single environment would want to default to the selection screen every time.

[inuonly]

i do like the idea of defaulting to the only one available as outlookhazy said, and if multiple then user can select as and when needed. If only one available we can always default to that without breaking anything. upvoted for the same .

[holysoles]

Here to chime in that this seems like a small change that is a nice UX win, particularly in smaller deployments that won't need more than a single environment.

[sammyke007]

+1 please!

[megosugit]

+1 same here, I spent time looking for a solution before finding this thread.

[toineenzo]

We need this!

[benjaminfrombe]

+1 !

[JasonEMartin]

+1 please.

[qmarquez]

+1

[lo97]

+1

[filcuk]

Please just upvote the discussion, there's no need to ping everyone with empty comments.

[OdinVex]

If we only have one...just default to it. If we have more than one, default to the earliest one created unless the user sets their preferred default environment from the existing user-allowed or none.

Minimal approach: At the very least if there is only one...just use it.