> For the complete documentation index, see [llms.txt](https://docs.archisketch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.archisketch.com/guide/intro-en/update-note/2025/202502/20250211.md). # \[2025.02.11] Professional Team Plan subscription launch Professional Team Plan launched ## Professional Team Plan Launch! Professional Team Plan Launch Announcement A new subscription service for small and medium-sized businesses has been released. Now use Archisketch’s collaboration features faster and more easily! In this update, along with the launch of the Professional Team Plan, various issue fixes and feature improvements were also made to enhance the user experience. Check out the improvements for a more stable and convenient service. ## Key Features of the Team Plan ️ Company-only domain provided * An independent website address exclusively for your company * Custom pages tailored to your brand image * Free customization of logos, theme colors, watermarks, and more account management system * Create accounts for as few as 3 and as many as 50 members * Role-based permission management for team members payment options * 20% discount when paying annually * Monthly installment payments available (₩189,000/month) * Support for domestic credit/debit card payments ## How to get started right away * Click the \[Subscribe to Professional Team] button [Quick link →](https://github.com/archisketch-dev-team/open-api-gitbook/tree/main/updates/team-plan-subscribe.md) * Enter company information * Company name * Company-only domain * Company information (optional) * Set the number of accounts and make payment * Service is available immediately after payment is completed ## Notes * Full refund available within 7 days of the initial subscription * Overseas card payments not supported * A separate enterprise contract is required for use by 51 or more users * Account additions/deletions are only possible within the contracted scope. For more details, please check the pricing page and user guide on Archisketch’s official website. ## Additional improvements and bug fixes #### Restriction on panorama tag settings * For some accounts, editing panorama tag information has been restricted to prevent the sharing of incorrect information. * Administrator, designer, and manager accounts have been kept able to edit tags as before. #### Hide bottom buttons in Panorama/720 Tour * Fixed the issue where bottom buttons covered the screen in mobile environments. * Improved so that bottom buttons are hidden by default by adding a specific URL parameter. #### Improved product name data structure * We improved data management efficiency by consolidating previously separately managed product names into a single structure. * A consistent structure has been maintained by organizing existing fields to ensure smooth multilingual support. *** Go to the Professional Team Plan guide --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.archisketch.com/guide/intro-en/update-note/2025/202502/20250211.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.