User Management for Brand Portals — SeeCommerce
More secure and scalable access: sign-ups with approval, clear roles and permissions, less friction for customers and admins.
Summary:
Results achieved:
- Self-service management of Brand Portal sign-ups.
- All preliminary agreements converted into active contracts.
- 80% of users found the User Management simple to use and easy to learn, thanks to the consistency of flows with the SeeCommerce platform.
Type of work:
Design and optimization of features (UX/UI)
Delivery:
Dedicated section in SeeCommerce for managing users of Brand Portals
Team:
Giacomo Dalia; Warda development team; CPO
My role:
UX/UI Designer — flow analysis, functional architecture, interface prototyping
Why true User Management was needed
Brand Portals were created to provide brands with a new external touchpoint, fully manageable within SeeCommerce. The first version was intentionally a minimal MVP from a user management perspective: it featured a single shared account, a temporary and conscious choice to allow customers to start testing the tool immediately, upload initial content, and provide useful feedback for development. This setup, despite its limitations, served as a testing ground: it allowed for rapid validation of the product's value and understanding of which aspects were priorities to strengthen in future sign-up management. Customers needed to decide who could enter and with what permissions, distinguishing different roles such as press, partners, or resellers. Initially, it was considered to integrate these users into the general User Management of SeeCommerce, but this choice created confusion and conflicts with existing accounts. Hence, the idea to create a separate but coherent User Management dedicated exclusively to the portals. The new solution introduced sign-ups with approval, targeted roles and permissions, and transparent visibility on the status of requests, reflecting the real complexity without burdening the experience.
Problem:
Integrating portal users into the general User Management created confusion (duplicate accounts, permission conflicts, different Press/Trade paths).
Solution:
Separate domains: a dedicated section for portals with flows designed specifically, maintaining visual and linguistic consistency with SeeCommerce.
The new architecture introduces three key states for individuals requesting access: Registration Requests (pending), [Accepted], and Rejected. From here, four operational subsections emerge:
Portal Users — a single view of approved users, with a list of portals they have access to within the tenant.
Registration Requests — management of requests for each portal: approve, reject, or leave pending.
Portal Roles — definition of roles and their respective permissions (e.g., single or bulk download allowed only for certain profiles).
Portal Permissions — list of available permissions to compose roles.
This structure resolves conflicts between accounts and clarifies "who can do what," allowing admins the freedom to model different rules for different targets (e.g., Press with immediate access to editorial materials and Trade with additional verification steps).
Designing simplicity for what is complex
Problem:
Too many manual steps and little visibility made management slow and fragile.
Solution:
Bringing everything "in-house": tenant admins consult, approve, or reject requests directly in SeeCommerce; decisions remain traceable and reviewable.
In practice, the experience for the admin is very smooth and intuitive: requests appear in an ordered list accompanied by essential information, allowing for clear evaluation of who is requesting access. Before approving, the administrator must choose the role to associate with the user: this mandatory step prevents granting access without adequate permissions and ensures consistency in usage rules. In cases where customers require stricter policies, the flow does not change but may include additional conditions, such as approval contingent on signing a contract or document verification. This way, governance is strengthened and remains secure, without burdening daily operations or slowing down work processes.
From pilot to daily operations: what really changes
Observed results
In concrete terms, the new User Management has consolidated the adoption of Brand Portals: 100% of preliminary agreements have been converted into active contracts, and there have been no dropouts during the rollout phase. The separation between the user system of the platform and that of the portals has prevented conflicts and duplications, while role management has clarified discretion over what can be seen and downloaded. From an operational standpoint, centralized approval in SeeCommerce has reduced manual steps and team back-and-forth by 20%, with a perceived improvement in efficiency: users reported beneficial rapid learning, attributed to the consistency of flows with the rest of the platform.
Conclusion
The project has transformed an "open" MVP into a controlled access system that grows with the needs of brands. The clarity of roles, traceability of decisions, and autonomy for admins have made Brand Portals more reliable in daily operations and SeeCommerce's offering more compelling to new clients.
User Management for Brand Portals — SeeCommerce
More secure and scalable access: sign-ups with approval, clear roles and permissions, less friction for customers and admins.
Summary:
Results achieved:
- Self-service management of Brand Portal sign-ups.
- All preliminary agreements converted into active contracts.
- 80% of users found the User Management simple to use and easy to learn, thanks to the consistency of flows with the SeeCommerce platform.
Type of work:
Design and optimization of features (UX/UI)
Delivery:
Dedicated section in SeeCommerce for managing users of Brand Portals
Team:
Giacomo Dalia; Warda development team; CPO
My role:
UX/UI Designer — flow analysis, functional architecture, interface prototyping
Why true User Management was needed
Brand Portals were created to provide brands with a new external touchpoint, fully manageable within SeeCommerce. The first version was intentionally a minimal MVP from a user management perspective: it featured a single shared account, a temporary and conscious choice to allow customers to start testing the tool immediately, upload initial content, and provide useful feedback for development. This setup, despite its limitations, served as a testing ground: it allowed for rapid validation of the product's value and understanding of which aspects were priorities to strengthen in future sign-up management. Customers needed to decide who could enter and with what permissions, distinguishing different roles such as press, partners, or resellers. Initially, it was considered to integrate these users into the general User Management of SeeCommerce, but this choice created confusion and conflicts with existing accounts. Hence, the idea to create a separate but coherent User Management dedicated exclusively to the portals. The new solution introduced sign-ups with approval, targeted roles and permissions, and transparent visibility on the status of requests, reflecting the real complexity without burdening the experience.
Problem:
Integrating portal users into the general User Management created confusion (duplicate accounts, permission conflicts, different Press/Trade paths).
Solution:
Separate domains: a dedicated section for portals with flows designed specifically, maintaining visual and linguistic consistency with SeeCommerce.
The new architecture introduces three key states for individuals requesting access: Registration Requests (pending), [Accepted], and Rejected. From here, four operational subsections emerge:
Portal Users — a single view of approved users, with a list of portals they have access to within the tenant.
Registration Requests — management of requests for each portal: approve, reject, or leave pending.
Portal Roles — definition of roles and their respective permissions (e.g., single or bulk download allowed only for certain profiles).
Portal Permissions — list of available permissions to compose roles.
This structure resolves conflicts between accounts and clarifies "who can do what," allowing admins the freedom to model different rules for different targets (e.g., Press with immediate access to editorial materials and Trade with additional verification steps).
Designing simplicity for what is complex
Problem:
Too many manual steps and little visibility made management slow and fragile.
Solution:
Bringing everything "in-house": tenant admins consult, approve, or reject requests directly in SeeCommerce; decisions remain traceable and reviewable.
In practice, the experience for the admin is very smooth and intuitive: requests appear in an ordered list accompanied by essential information, allowing for clear evaluation of who is requesting access. Before approving, the administrator must choose the role to associate with the user: this mandatory step prevents granting access without adequate permissions and ensures consistency in usage rules. In cases where customers require stricter policies, the flow does not change but may include additional conditions, such as approval contingent on signing a contract or document verification. This way, governance is strengthened and remains secure, without burdening daily operations or slowing down work processes.
From pilot to daily operations: what really changes
Observed results
In concrete terms, the new User Management has consolidated the adoption of Brand Portals: 100% of preliminary agreements have been converted into active contracts, and there have been no dropouts during the rollout phase. The separation between the user system of the platform and that of the portals has prevented conflicts and duplications, while role management has clarified discretion over what can be seen and downloaded. From an operational standpoint, centralized approval in SeeCommerce has reduced manual steps and team back-and-forth by 20%, with a perceived improvement in efficiency: users reported beneficial rapid learning, attributed to the consistency of flows with the rest of the platform.
Conclusion
The project has transformed an "open" MVP into a controlled access system that grows with the needs of brands. The clarity of roles, traceability of decisions, and autonomy for admins have made Brand Portals more reliable in daily operations and SeeCommerce's offering more compelling to new clients.
User Management for Brand Portals — SeeCommerce
More secure and scalable access: sign-ups with approval, clear roles and permissions, less friction for customers and admins.
Summary:
Results achieved:
- Self-service management of Brand Portal sign-ups.
- All preliminary agreements converted into active contracts.
- 80% of users found the User Management simple to use and easy to learn, thanks to the consistency of flows with the SeeCommerce platform.
Type of work:
Design and optimization of features (UX/UI)
Delivery:
Dedicated section in SeeCommerce for managing users of Brand Portals
Team:
Giacomo Dalia; Warda development team; CPO
My role:
UX/UI Designer — flow analysis, functional architecture, interface prototyping
Why true User Management was needed
Brand Portals were created to provide brands with a new external touchpoint, fully manageable within SeeCommerce. The first version was intentionally a minimal MVP from a user management perspective: it featured a single shared account, a temporary and conscious choice to allow customers to start testing the tool immediately, upload initial content, and provide useful feedback for development. This setup, despite its limitations, served as a testing ground: it allowed for rapid validation of the product's value and understanding of which aspects were priorities to strengthen in future sign-up management. Customers needed to decide who could enter and with what permissions, distinguishing different roles such as press, partners, or resellers. Initially, it was considered to integrate these users into the general User Management of SeeCommerce, but this choice created confusion and conflicts with existing accounts. Hence, the idea to create a separate but coherent User Management dedicated exclusively to the portals. The new solution introduced sign-ups with approval, targeted roles and permissions, and transparent visibility on the status of requests, reflecting the real complexity without burdening the experience.
Problem:
Integrating portal users into the general User Management created confusion (duplicate accounts, permission conflicts, different Press/Trade paths).
Solution:
Separate domains: a dedicated section for portals with flows designed specifically, maintaining visual and linguistic consistency with SeeCommerce.
Designing simplicity for what is complex
The new architecture introduces three key states for individuals requesting access: Registration Requests (pending), [Accepted], and Rejected. From here, four operational subsections emerge:
Portal Users — a single view of approved users, with a list of portals they have access to within the tenant.
Registration Requests — management of requests for each portal: approve, reject, or leave pending.
Portal Roles — definition of roles and their respective permissions (e.g., single or bulk download allowed only for certain profiles).
Portal Permissions — list of available permissions to compose roles.
This structure resolves conflicts between accounts and clarifies "who can do what," allowing admins the freedom to model different rules for different targets (e.g., Press with immediate access to editorial materials and Trade with additional verification steps).
Problem:
Too many manual steps and little visibility made management slow and fragile.
Solution:
Bringing everything "in-house": tenant admins consult, approve, or reject requests directly in SeeCommerce; decisions remain traceable and reviewable.
From pilot to daily operations: what really changes
In practice, the experience for the admin is very smooth and intuitive: requests appear in an ordered list accompanied by essential information, allowing for clear evaluation of who is requesting access. Before approving, the administrator must choose the role to associate with the user: this mandatory step prevents granting access without adequate permissions and ensures consistency in usage rules. In cases where customers require stricter policies, the flow does not change but may include additional conditions, such as approval contingent on signing a contract or document verification. This way, governance is strengthened and remains secure, without burdening daily operations or slowing down work processes.
Observed results
In concrete terms, the new User Management has consolidated the adoption of Brand Portals: 100% of preliminary agreements have been converted into active contracts, and there have been no dropouts during the rollout phase. The separation between the user system of the platform and that of the portals has prevented conflicts and duplications, while role management has clarified discretion over what can be seen and downloaded. From an operational standpoint, centralized approval in SeeCommerce has reduced manual steps and team back-and-forth by 20%, with a perceived improvement in efficiency: users reported beneficial rapid learning, attributed to the consistency of flows with the rest of the platform.
Conclusion
The project has transformed an "open" MVP into a controlled access system that grows with the needs of brands. The clarity of roles, traceability of decisions, and autonomy for admins have made Brand Portals more reliable in daily operations and SeeCommerce's offering more compelling to new clients.