# SaaS with user-generated content (/docs/use-cases/saas-user-generated-content) # Reuse one moderation model across SaaS features [#reuse-one-moderation-model-across-saas-features] Represent comments, profiles, public pages, templates, uploads, and marketplace extensions as distinct entities without creating a new safety integration for every collaborative feature. User-generated content often enters a SaaS product gradually: a profile field, a shared page, a comment thread, a file preview, then a public template gallery. Insion gives all of those features a common policy and action layer, avoiding a new engineering project each time collaboration expands. ## Avoid a separate safety backlog for every feature [#avoid-a-separate-safety-backlog-for-every-feature] An abusive comment can damage a team workspace. A phishing link in a public template can affect users beyond the account that created it. Spam in shared galleries reduces discovery quality. When each feature owns its own filter, enforcement becomes inconsistent and account history fragments across services. The cost extends beyond classification. Your team also has to retain decisions, deliver status changes, coordinate user restrictions, protect sensitive accounts, and create a dispute process. Insion connects those operational pieces. ## Keep each product object distinct [#keep-each-product-object-distinct] Moderate workspace comments, public pages, templates, profile fields, project descriptions, uploaded images, embedded links, marketplace extensions, and community resources. Keep the workspace, plan, visibility, feature, or customer context attached to each decision. This flexibility lets a multi-product SaaS platform share moderation operations without flattening every feature into an indistinguishable item. ## Match moderation timing to feature visibility [#match-moderation-timing-to-feature-visibility] Check a public template or profile before publication. Evaluate collaboration content in the background when it should save immediately. Both approaches apply your current rules. Spam, Phishing, Hate and harassment, Privacy and doxxing, Adult content, and Violence offer broad coverage. Custom rules can allow legitimate sales templates and security examples while flagging credential-harvesting pages, targeted abuse between workspace members, repeated promotional submissions, or links prohibited by your marketplace policy. ## Give each SaaS feature the right response [#give-each-saas-feature-the-right-response] | Feature and result | Possible product response | | -------------------------------------------- | ------------------------------------------------- | | A public template is flagged | Keep it unpublished | | A private workspace comment is flagged | Notify or route it to the workspace administrator | | A profile becomes compliant after an edit | Restore the relevant visibility or access | | An enterprise account needs special handling | Protect it from automatic account action | Each feature can respond differently while sharing the same rules and account history. Developers can follow the [quickstart](/docs/quickstart) or choose an official [SDK](/docs/sdks) when they are ready to implement the first flow. ## Turn one status into behavior for each feature [#turn-one-status-into-behavior-for-each-feature] A flagged template can remain unpublished, while a flagged private comment can go to an administrator. Each decision identifies the affected item and preserves its feature context, allowing the product to respond appropriately without building a separate moderation system. User events communicate suspension, compliant, and ban changes across the SaaS account. Configure the flagged-record count that triggers suspension. Protected accounts avoid automated actions when customer context requires manual handling, and appeals give eligible suspended users a structured review route. Configurable rules, retained decisions, immediate and background checks, account actions, protection, and appeals form a platform-wide moderation layer. Your next collaborative feature can reuse it instead of adding another safety backlog. ## Establish a reusable rollout pattern [#establish-a-reusable-rollout-pattern] Choose the public feature with the clearest policy, such as a template gallery, and begin in test mode. Insion evaluates and stores records without emitting moderation webhooks or automatically changing user state, allowing product and support teams to review outcomes before customers are affected. Agree on a small set of content types and shared context so teams do not create incompatible names for the same content. Keep customer identifiers useful for routing, but avoid unnecessary customer data. Protect enterprise or specially managed accounts where automatic suspension would conflict with customer operations. When you expand to comments, profiles, or marketplace extensions, reuse this foundation and add only the actions unique to that feature.