Account flows
Consider how people sign in and manage access to their space.
Web / a space for each person
Web portals and private areasThe right access, for every user.
A portal brings dedicated content and actions together for recognised users. Accounts, permissions and administration are designed around what each person needs to access.
Inside the project
A project takes shape.
Layer by layer.
Structure, details and interactions come together in one coherent experience.
- 01Structure
- 02Content
- 03Interaction
A closer look
Make access part of the design.
The relationship between users, content and permissions is the starting point. Someone may need to read a document, another person to update it and an administrator to manage access. Defining those boundaries early helps the interface and the underlying information stay coherent.
Private content
Define visibility according to roles and relationships.
Editing tools
Provide the agreed controls for updating information and managing the platform.
A place to start
The project in context.
A portal can support an event, a community or a shared collection of information. EWA Live in the HexaDev portfolio is a reference for a public website alongside a private event platform.
Projects ↗Frequently asked questions
Before we begin.
Can a private area be added to an existing site?
It depends on the current technology. It might be integrated directly or built as a connected application.
How are permissions decided?
Start with each resource and action, then decide which roles may read or change it. Those rules must also be enforced on the server.
What about timing?
That depends on the idea, the content and any tools involved. We can discuss it once we understand what the project would look like.