Overview

In Khoros Aurora Community, file attachment settings are configured from Admin Settings > Features > Content Features, and those settings can also be adjusted at the board level.^[1] Knowledge Base boards have their own settings path under Settings > Community Structure, where the board’s Content Features section includes File Attachments.^[2]

If you save a higher community-wide value but the Knowledge Base article editor still shows Max file size: 100 MB, review the Knowledge Base board setting next. Aurora documents both the community-wide setting and the Knowledge Base board-level setting, so the effective limit for KB articles must be verified in the board itself as well.^[1][2]

Solution

Use the following steps when you need a higher attachment limit on Knowledge Base articles.

1. Review the community-wide attachment setting.

   1. Go to Admin Settings > Features > Content Features.^[1]
   2. Open File Attachments.
   3. Review Maximum attachment file size for upload (MB).

2. Review the Knowledge Base board attachment setting.

   1. Sign in to the community as an Admin.
   2. Open the Account menu and click Settings.^[2]
   3. Go to the Community Structure page.
   4. On the Knowledge Base whose settings you want to edit, click the gear icon.
   5. Click Edit.
   6. In the Content Features tab, open File Attachments.^[2]
   7. Set Maximum attachment file size for upload (MB) to the same value you want to allow on KB articles.
   8. Save the change.

3. Verify the effective limit on the KB article editor.

   1. Open a Knowledge Base article create or edit page.
   2. In the Attachments area, confirm the editor now shows the updated limit instead of Max file size: 100 MB.
   3. Upload a test file larger than 100 MB to confirm the change is effective.

If the Settings page does not let you enter or save the value you need, contact Support and provide all of the following:

• your base community URL
• whether the change is needed for the whole community or only for a specific Knowledge Base board
• the exact value you want to allow, in MB
• the exact validation error text shown in the Settings page
• a screenshot of Admin Settings > Features > Content Features > File Attachments
• a screenshot of the Knowledge Base article editor showing the current Max file size text
• the Knowledge Base board name or URL
• a sample file size that is currently being blocked

<supportagent>

Use the following Support-only workflow when the customer needs a file attachment limit above the value currently accepted in the Admin UI.

1. Confirm the customer’s target scope first: whole community or only a specific Knowledge Base board.
2. Check whether the customer is blocked before save or after save:
   • If the customer cannot enter or save the requested value and the Settings page shows a validation error such as This value must be less than or equal to 1, treat this as a Support-managed tenant-side limit review, not only as a board-override problem.
   • If the customer can save the higher value at the community level but the KB editor still shows Max file size: 100 MB, check the KB board’s File Attachments override next.
3. If the Admin UI is blocking the requested value, raise the standard Support/SaaS config-change path for the target environment first. In the investigated ticket history, Support raised the tenant-side ceiling on stage before the 500 MB value could be used there, then repeated the production-side deployment only after staging validation succeeded.
4. After the tenant-side change is deployed, verify the customer or Support can save the required value under Admin Settings > Features > Content Features > File Attachments.
5. Then verify the specific Knowledge Base board under Settings > Community Structure > gear icon > Edit > Content Features > File Attachments and align its board-level value with the intended KB limit.
6. Validate on stage with an actual file larger than the previous limit before requesting the same change in production.
7. If production shows 500 at the community level but the KB article editor still shows 100 MB, do not treat that as propagation delay. Check the KB board override immediately.

Nuances:

• The public docs confirm that file attachment settings exist at both the community level and the board level, so both layers must be checked for KB uploads.^[1][2]
• Do not broaden the customer’s request unnecessarily. If they want the increase only for KB articles, keep the investigation focused on the KB board unless the Admin UI is blocking the value before save.
• When collecting escalation data for the config-change path, include the base URL, environment, requested MB value, exact validation error text, screenshots of the Settings page and KB editor, the KB board URL or display ID, and the size of a sample file that is failing.

</supportagent>

References

1. Aurora: Configure File Attachment settings for the community
2. Aurora: Edit knowledge base board settings