Skip to content

Admin Settings

Three permission sets ship with the package. Every user of the component needs at least the base set.

Permission SetRequired forGrants
Tucario Files (base)Every user of the componentApp access (“Smarter Files by Tucario”), CRUD on the Tucario_File_Visibility__c junction object, access to TucarioFileDownloadController and TucarioVisibilityController
Tucario - Manage File CategoriesAdmins and category ownersCustom permission Tucario_Manage_Categories — assign categories on files via “Set Category”, and bypass category filtering (these users always see every file)
Tucario - View Private DocumentsAdmins, HR, compliance officersCustom permission Tucario_View_Private_Documents — view files marked private by other users

Upload rules — allowed extensions, excluded extensions, and max size — are configured per component instance through the design properties in App Builder, not globally. See Component Setup for the full property list.

This means you can have different upload rules on different record pages, or even multiple instances on the same record page with different rules.

Visibility Rules — Tucario_Visibility_Rule__mdt

Section titled “Visibility Rules — Tucario_Visibility_Rule__mdt”

Visibility rules are stored as Custom Metadata Type records and managed through the Configuration Wizard — not edited directly in Setup.

FieldTypePurpose
CategoryTextThe document type name (e.g., HR Documents, Contracts). Files reference this string in their Visibility_Category__c field.
Permitted RolesLong Text AreaSemicolon-separated list of role DeveloperName values (e.g., CEO;HR_Manager;HR_Specialist). Users whose role matches one of these can see files in this category.
Is ActiveCheckboxWhether the rule is enforced. Inactive rules behave as if they don’t exist (the category falls back to default-open).
DescriptionTextAdmin-facing description of what the category contains.

File Visibility Junction — Tucario_File_Visibility__c

Section titled “File Visibility Junction — Tucario_File_Visibility__c”

Smarter Files creates a custom object junction record for each file managed under Isolated storage mode (and for any file with a category or private flag, regardless of mode).

FieldTypePurpose
Content Document IdText (External ID, Unique)Reference to the Salesforce ContentDocument. One junction record per file per parent record.
Parent Record IdText (18)The 18-character ID of the record the file is attached to.
Visibility CategoryText (80)The category name from Tucario_Visibility_Rule__mdt. Empty means no category restriction.
Is PrivateCheckboxTrue if the file has been marked private.
Owner IdLookup (User)The user who marked the file private. Required when Is Private is true (enforced by the Owner_Required_When_Private validation rule).

Auto-naming: records use the format FV-{0000}.

Sharing model: ReadWrite. SOQL/DML on this object runs in USER_MODE, so users only see and modify junction records they have access to.

API NameUsed by
Tucario_Manage_CategoriesGranted via the Tucario - Manage File Categories permission set. Controls visibility of the Set Category menu item and bypasses category-based filtering.
Tucario_View_Private_DocumentsGranted via the Tucario - View Private Documents permission set. Allows seeing private files owned by other users.

You can assign these custom permissions through your own permission sets if you want to bundle them with org-specific roles instead of using the shipped permission sets.

Two controllers are accessible from Lightning components — both run with sharing and use USER_MODE SOQL/DML:

  • TucarioFileDownloadController — file CRUD, upload/download, public link creation, category assignment, private flag toggling.
  • TucarioVisibilityController — wizard backend (role list, rule deployment, deployment status polling), batch migration controls, permission checks.

Grant access via the Tucario Files permission set (already enabled there) — there’s normally no reason to enable these classes through other permission sets.