Meta tags:
description= Custom fields enhance your documentation by allowing tailored metadata, improving organization, and supporting integrations for effective content management.;
Headings (most frequently used words):
custom, fields, field, documentation, index, when, to, use, access, create, preserve, values, across, languages, manage, configure, in, an, article, team, auditing, best, practices, faq, types, document360, top, features, support, contact, us,
Text of the page (most frequently used words):
the (80), field (65), custom (47), #fields (39), article (30), and (25), for (23), values (22), api (18), settings (15), only (14), are (13), type (13), language (12), select (12), can (11), create (11), edit (11), click (11), knowledge (10), base (10), portal (10), all (10), text (10), documentation (9), when (9), delete (9), via (9), from (9), articles (8), content (8), this (8), default (8), version (8), cannot (8), with (7), over (7), enabled (7), that (7), across (7), page (7), team (6), document360 (6), update (6), contributors (6), after (6), your (6), languages (6), more (6), support (5), integrations (5), creation (5), set (5), per (5), updated (5), use (5), help (5), data (5), date (5), icon (5), characters (5), you (5), 2026 (5), workflow (4), management (4), external (4), editor (4), next (4), carried (4), other (4), new (4), created (4), project (4), users (4), must (4), specific (4), value (4), read (4), option (4), description (4), product (4), navigate (4), preserve (4), note (4), open (4), unique (4), copy (4), left (4), navigation (4), input (4), review (4), about (3), status (3), analytics (3), site (3), features (3), troubleshooting (3), yes (3), versions (3), them (3), add (3), permissions (3), roles (3), permission (3), manage (3), stored (3), published (3), not (3), managed (3), what (3), deleting (3), deleted (3), existing (3), one (3), creating (3), see (3), enter (3), example (3), before (3), changed (3), dropdown (3), view (3), auditing (3), decision (3), available (3), toggle (3), access (3), single (3), name (3), want (3), structured (3), metadata (3), ask (3), policy (2), our (2), com (2), contact (2), feedback (2), seo (2), drive (2), extensions (2), private (2), hosting (2), request (2), managing (2), issues (2), based (2), pages (2), was (2), automatically (2), needed (2), carry (2), unless (2), latest (2), becomes (2), through (2), permanently (2), removes (2), its (2), where (2), used (2), restored (2), different (2), required (2), clean (2), unused (2), longer (2), panel (2), system (2), tooltip (2), entry (2), needs (2), actions (2), including (2), updating (2), information (2), options (2), once (2), configure (2), configured (2), dialog (2), code (2), carryover (2), level (2), setting (2), pane (2), bar (2), number (2), multiple (2), predefined (2), list (2), multi (2), line (2), types (2), appears (2), grid (2), optional (2), consistent (2), track (2), such (2), feature (2), release (2), let (2), trees (2), claude (2), chatgpt (2), markdown (2), llms (2), ctrl (2), search (2), glossary (2), october (2), docs (2), file (2), index (2), soc2, cookie, privacy, trust, center, terms, careers, culture, 3000, rating, ticket, deflector, platform, assistant, top, enterprise, readiness, security, migration, demo, resources, pricing, customers, getting, started, endpoint, implementing, audience, segregation, platforms, choices, related, previous, helpful, workspace, fully, editable, authors, translate, who, modify, useful, automated, scripts, does, every, happens, modified, correct, change, faq, noise, keep, populated, integration, script, enable, prevent, manual, overrides, generously, brief, format, prevents, inconsistent, plan, decide, upfront, whether, another, best, practices, captured, well, within, activity, log, carrying, save, appropriate, each, locate, section, header, have, tree, associated, caution, checkbox, toolbar, confirmation, confirm, selected, copies, identifier, calls, details, changes, apply, hover, reveal, also, applies, during, clone, replicate, move, backup, restore, operations, marked, even, disabled, any, contributor, updates, directly, non, stops, syncing, same, continue, usual, undone, manually, maintained, going, forward, how, sync, works, off, near, button, projects, numeric, true, false, boolean, picker, 150, area, character, limit, guidance, displayed, entered, placeholder, stores, below, mandatory, maximum, following, displays, certain, exclusively, keeping, integrating, requires, enforce, covered, compliance, teams, organise, effectively, maintain, require, may, owner, these, then, attach, additional, categories, instead, relying, tags, title, define, own, capture, prev, summary, plain, print, listen, focus, minute, jun, sep, powered, press, community, self, service, november, notes, integrate, manager, domain, customization, import, export, reminder, collaboration, tasks, interactive, templates, variables, snippets, advanced, sign, role, control, workspaces, key, readers, creators, eddy, invite, customize, publish, quick, start, discover, exploring, further, fetch, complete, https, txt,
Text of the page (random words):
custom fields documentation index fetch the complete documentation index at https docs document360 com llms txt use this file to discover all available pages before exploring further quick start create an article review article publish article customize site invite users set up roles permissions track analytics eddy ai features for creators for readers for integrations key features multiple workspaces languages role based access control single sign on private hosting advanced editor templates variables snippets glossary drive file management custom fields interactive decision trees collaboration tasks custom workflow review reminder import export project site customization custom domain integrations extensions analytics feedback manager api documentation integrate with document360 manage your api docs release notes november 2026 12 11 1 october 2026 12 10 2 october 2026 12 10 1 help troubleshooting self service support ask for a feature community glossary search ctrl k press ctrl k to open search powered by custom fields updated on sep 7 2026 published on jun 13 2026 6 minute s read focus listen print copy page copy as markdown for llms view as markdown view the page as plain text open in chatgpt ask chatgpt about this page open in claude ask claude about this page article summary prev next custom fields let you attach additional structured data to articles page categories decision trees and api documentation instead of relying only on default metadata such as tags seo title or description custom fields let you define your own fields and capture information specific to your documentation workflow for example a product documentation team may want to add fields such as product version feature owner release status or content review date these fields are created at the project level and then configured per article custom fields help teams organise content more effectively maintain consistent data across articles and support integrations that require structured metadata from the knowledge base when to use custom fields your team needs to track metadata not covered by document360 s default fields for example a product version number or a compliance review date you want to enforce consistent data entry across all articles in a project you are integrating document360 with an external system that requires structured fields from your knowledge base you want certain field values to be managed exclusively via the api keeping them read only in the portal access custom fields navigate to settings knowledge base portal in the left navigation bar select custom fields in the left navigation pane the custom fields page displays a grid of all existing custom fields including the field name and field type create a custom field on the custom fields page click create custom field in the create custom field dialog configure the following field description field name a unique name for the field mandatory maximum 30 characters field type the type of data the field stores cannot be changed after creation see field types below placeholder text optional content that appears in the field before a value is entered help text optional guidance for contributors displayed as a tooltip next to the field in article settings edit via api only when enabled the field is read only in the portal values can only be updated through the api click create once created the field appears in the grid and becomes available in article settings note the field type cannot be changed after creation if a different field type is required delete the existing field and create a new one field types field type description character limit text single line text input 30 characters text area multi line text input 150 characters dropdown single select select one option from a predefined list 30 characters per option dropdown multi select select multiple options from a predefined list 30 characters per option date date picker input boolean true false toggle number numeric input preserve field values across languages the preserve field values across languages toggle is enabled by default for all projects when enabled custom field values set on the default language are automatically carried over to all other language versions to access this setting navigate to settings knowledge base portal in the left navigation bar select custom fields in the left navigation pane click the more icon near the create custom field button select preserve field values across languages to toggle the setting on or off how sync works at the field level when enabled if a contributor updates a field value directly in a non default language article that specific field stops syncing from the default language for that article other fields in the same article continue to carry over as usual this cannot be undone the field must be manually maintained in that language going forward when disabled field values updated in the default language are no longer carried over to any other language versions note the carryover also applies during clone replicate move and backup restore operations fields marked as edit via api only can only be updated via the api even after carryover manage custom fields navigate to settings knowledge base portal custom fields and hover over a field to reveal the available actions edit click the edit icon update the field details and click update changes apply to all articles where the field is used copy unique code click the more icon and select copy unique code this copies the field s unique identifier for use in api calls delete click the more icon and select delete or select the checkbox next to the field and click delete selected from the toolbar type yes in the confirmation dialog and click delete to confirm caution deleting a custom field permanently removes its values from all associated articles deleted fields cannot be restored note users with editor permissions can create edit and delete custom fields for custom roles the custom fields permission must be enabled to update custom field values in article settings users must have the article decision tree settings permission contributors can update custom field values unless the field is configured as edit via api only configure custom fields in an article once a custom field is created contributors can set values for it in article settings open the article in the knowledge base portal click the more icon in the article header and select more article options in the article settings panel locate the custom fields section enter or select the appropriate value for each field click save note custom field values are stored for the latest published version of an article and are not version specific for information on carrying field values across languages see preserve field values across languages team auditing all custom field actions are captured in team auditing including creating updating and deleting fields as well as updating field values within articles navigate to settings knowledge base portal team auditing to view the activity log best practices plan your fields before creating them field type cannot be changed after creation decide upfront whether a field needs to be text dropdown date or another type use help text generously contributors see the help text as a tooltip in article settings a brief description of what to enter for example enter the product version in x x x format prevents inconsistent data entry use edit via api only for system managed fields if a field is populated by an external integration or script enable edit via api only to prevent manual overrides in the portal clean up unused fields unused custom fields add noise to article settings delete fields that are no longer needed to keep the article settings panel clean faq can i change the field type after creating a custom field no the field type cannot be modified after creation if a different field type is required delete the existing field and create a new one with the correct type what happens when a custom field is deleted deleting a custom field permanently removes it and all its values from every article where it was used deleted fields cannot be restored what does the edit via api only option do when enabled contributors cannot modify the field value from the portal the field becomes read only in article settings and can only be updated through the api this is useful for fields managed by external integrations or automated scripts are custom field values stored per article version no custom field values are stored for the latest published version of an article and are not version specific who can create and manage custom fields users with editor permissions can create edit and delete custom fields for custom roles the custom fields permission must be enabled contributors can update field values in article settings unless the field is set to edit via api only do custom field values carry over when i add a new language to my project yes custom field values set on the default language are automatically carried over to all other language versions when a new language workspace is created the carried over values are fully editable per language so authors can update or translate them as needed was this article helpful yes no previous article managing workflow status next article troubleshooting content management issues related articles custom pages editor choices content creation implementing audience based content segregation with custom fields for external platforms content management troubleshooting content management issues managing endpoint articles api documentation getting started with api documentation document360 customers pricing resources request a demo migration request security private hosting enterprise readiness top features knowledge base portal knowledge base site knowledge base assistant integrations and extensions platform api analytics workflow ticket deflector drive seo support documentation support status feedback contact us contact us support document360 com rating 4 7 3000 about us our team our culture careers terms trust center privacy policy cookie policy soc2
|
