Feature preview
When managing multiple sites with the same content system, the isolation of user groups and permissions should be divided into two layers: first, define the site boundary, what operations the account can perform in which site; then, define the group boundary, the corresponding readable and writable scope for editors, operators, and external authors. AnQiCMS uses multi-site management and user groups with VIP groups to implement these two layers, and make a data backup before changing permissions, recover deleted documents from the recycle bin.
When managing multiple sites with a single content system, how to isolate user groups and permissions? The answer is to design in two layers: the first layer is the site boundary, which determines which sites an account can see; the second layer is the group boundary, which determines what actions it can take in these sites. Mixing the two together will lead to issues such as 'I only want external authors to submit articles, but they can edit others' articles'.
Under multi-site management, all sites share a set of programs and databases, and the account system is also shared. Therefore, the first step is not to assign permissions but to define scopes: which sites does this account belong to, and is cross-site login allowed. The approach is to define scopes based on organizations rather than individuals, for example, the 'Brand Site Group' includes the main site and two promotional sites, and the 'Agent Site Group' includes several customer sites. After the scope is defined, roles have objects to act on, otherwise the word 'operation' has different meanings in two sites, and permissions cannot be verified.
The user group and VIP group manage the accessible range, not the job name. The group should be written as a verifiable description to be effective: which menus can be accessed in the background, which draft columns can be viewed, whether they can be published or only submitted. The table below provides a common hierarchical method, and the two columns on the right are the key criteria for isolation.
| Group | Operable range | Common mismatch |
|---|---|---|
| Site administrator | All content and column settings within a single site | Cross-site range has been given, a single misoperation affects multiple sites |
| Edit | Column content of sites already assigned, including review | Can only view and not review, manuscripts pile up in the queue |
| Operation | Publication and topping of specified columns | Can change the template, page style is arbitrarily overwritten |
| External Author | Submit draft, cannot be published | Content review not open, manuscript goes live directly |
The criteria for grouping are verifiable actions: let each group perform a typical operation to see if it can succeed, and then let it perform an out-of-bound operation to see if it is blocked. Only the groups that can be verified are isolated, and those that cannot be verified are just named.
The first is permission叠加：The account is an editor on site A, and an administrator on site B, after logging in, the interface is displayed according to the highest permission, and it is easy to bring the habits of site B into site A.The second is a broken review chain: The content submitted by external authors will go through content review within a single site, and when crossing sites, if the same link is not opened in site B, the online results of the same article will be different on the two sites.The third type is difficult to recycle: after the cooperation ends, only the relationship with one site is deleted, and the account can still access another site. The corresponding approach is to default close the high-risk operation domain, and not assign actions such as backup and upgrade to the daily group;Adjust permissions site by site, regularly recycle accounts that no longer cooperate from all sites.
Before making changes, first create a data backup, including the current account and group relationship along with the content. After making changes, check two things: whether the new group can complete the tasks assigned to it, and whether the people who were originally allowed in are correctly blocked out. When a document is deleted incorrectly, it is cheaper to recover it from the Recycle Bin than to restore from a backup, but the Recycle Bin has a retention period, and if an accidental deletion is found, it must be handled on the same day.
Question: The groups have already been split by role. Do we need to divide the range by site as well?Answer: Yes. Role explanations indicate what can be done, and range explanations indicate where it can be done. When the same program manages multiple sites, if the range layer is missing, role permissions will take effect on all sites at the same time.
Ask: Is the VIP group the same as the user group on the backend?Answer: No, they are not the same purpose. Both manage the scope of access, the user group is for backend operation permissions, and the VIP group is for the level of content that front-end readers can see, such as paid columns and non-paid content. Define separately when designing, do not use a set of groups to bear both types of judgments at the same time.
Ask: Can external authors only open one site?Answer: Yes, limit the submission relationship to that site, and at the same time confirm that the site has opened the content review process. Only submit and do not publish, cooperate with the review to form a complete link.
Preview
When batch modifying the keywords of old columns, it is suitable to replace them station-wide with clear scope, unambiguous matching strings, and no semantic judgment involved. The mechanical changes should be made for each article depending on the context. The boundary lies in whether the replacement may harm homophones, and whether it affects the semantics of the title and description. Before starting, run a preview of the replacement list, and confirm that the backup and recycle bin can handle any unintended changes.
Preview
The custom content model solves the problem of decoupling the content structure from business fields. When the article type is hardcoded, adding a parameter, scope, or attachment field requires changing the code and database structure; after changing to a configurable content model, fields can be defined in the background and can enter the editing page and list call, historical data is compatible with null values, and there is no need to go through a release cycle for a single structural change.
Preview
AI automatically tags, automatically matches titles with images, and generates TDK, which can save the repetitive labor of entry, but the product itself may still be wrong: misaligned tags can distort in-site search, and image matching should consider the source and watermark. The review should be done before the draft is converted to a formal version, and sensitive word filtering and keyword replacement are just at the bottom layer, not replacing manual judgment of facts and compliance. Before mass production, the review should be passed first, and then scheduled for release.
