
Portals are now equipped with access controls, ensuring that both confidential and publicly available information are managed and shared effectively. Three distinct levels of access are being introduced to cater to different user requirements, offering comprehensive control to administrators and seamless access to users.

Public
Designed for open access, public portals can be viewed by anyone without requiring login, making it easy to share general information broadly.
Use case: A SaaS company maintains a public changelog and roadmap to keep all users, prospects, and stakeholders informed about new features and upcoming releases. This allows anyone to stay up to date without needing an account.
Restricted
This level offers domain-specific access or individual email access, allowing certain external users to access the portal while keeping information private from the general public.
Use case: A software vendor provides a feature request portal for key customers and partners. They configure access to allow specific external users (e.g., @partner.com emails or individual customer addresses) to view and track relevant updates while ensuring unauthorized users cannot see restricted content.
Internal (Coming Soon)
This level is restricted to users with an email domain that matches your organization’s domain, which can be configured by a Released admin. It requires authentication to ensure only authorized users can view sensitive information.
Use case: A company wants to share its product roadmap internally but restricts access to employees with a corporate email (e.g., @company.com). This ensures that only team members can view confidential plans, preventing external visibility.
For more details, see the documentation.
Sign in via Atlassian, Google or magic link

To make authentication as seamless as possible, Released currently offers three flexible sign-in options:
Atlassian
Ideal for teams already using Jira or other Atlassian products, this option allows users to sign in with their Atlassian account. This ensures a smooth experience, leveraging existing credentials without the need for additional passwords.
A convenient choice for those using Google Workspace or Gmail, this option lets users sign in quickly with their Google credentials. It simplifies authentication by reducing the need to remember separate login details while maintaining security through Google’s authentication protocols, including multi-factor authentication (if enabled).
Email – Magic Link
For users who prefer a password-free experience, the magic link option allows sign-in via email. Simply enter your email address, and a one-time login link is sent directly to your inbox.
User verification
You can now control who accesses your private widgets and pages with User Verification. By generating secure authentication tokens, you ensure that only authorized users can view sensitive content—while keeping the experience seamless for your team and customers.
✅ Secure access – Keep private content restricted to the right people.
✅ Seamless experience – No extra logins or friction for users.
For all the technical details, see the documentation.