Question about workspace setup before first interaction

[tornidomaroc-web]

Hi,

I was looking into the first user experience and had a quick question about the initial flow.

It seems users are required to choose or create a workspace (and sometimes select a region) before they can interact with the core product.

In many tools, users can perform a first action immediately before making structural decisions like this.

Was this flow designed intentionally to prioritize workspace setup before first interaction?

Curious about your thinking here.

Thanks

[ArtyomSavchenko]

Hi @tornidomaroc-web
At the moment users without account can see some workspaces in read-only mode
For example, we have enabled guest access for our workspace on the staging server: https://front.hc.engineering/workbench/platform/tracker/all-issues.
We also plan to build a community support portal with guest access on the production huly.app instance.
The same portal can be used for initial acquaintance with the product.

Would that solve your problem?

[tornidomaroc-web]

Hi Artyom Savchenk, Guest access helps with visibility, but it still keeps users in a passive state—they can see, but not act. The real gap seems to be reaching a first meaningful action early. Curious if you’ve observed how often users move from viewing to actually creating their first item. Best, Abo Jad

…

On Mon, 6 Apr 2026 at 09:40 Artyom Savchenko ***@***.***> wrote: Hi @tornidomaroc-web <https://github.com/tornidomaroc-web> At the moment users without account can see some workspaces in read-only mode For example, we have enabled guest access for our workspace on the staging server: https://front.hc.engineering/workbench/platform/tracker/all-issues . We also plan to build a community support portal with guest access on the production huly.app instance. The same portal can be used for initial acquaintance with the product. Would that solve your problem? — Reply to this email directly, view it on GitHub <#10721 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/CANBVWQ32DFHRFGEY2OFLED4UNUONAVCNFSM6AAAAACXMEQ4OOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNBWGIYDQOI> . You are receiving this because you were mentioned.Message ID: ***@***.*** com>