{"id":403,"date":"2026-02-25T10:17:25","date_gmt":"2026-02-25T10:17:25","guid":{"rendered":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/"},"modified":"2026-02-25T10:17:25","modified_gmt":"2026-02-25T10:17:25","slug":"bpmn-process-scope-effective-modelling","status":"publish","type":"docs","link":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/","title":{"rendered":"Scoping Your Process Models Effectively"},"content":{"rendered":"<p>Many beginners confuse BPMN modeling scope with the entire business process. That\u2019s a common misstep. The process scope isn\u2019t about capturing every detail\u2014it\u2019s about defining what\u2019s included and what\u2019s not. Think of it as drawing a boundary around a conversation: not every side discussion belongs in the main flow.<\/p>\n<p>I\u2019ve seen models fail not from incorrect symbols, but from unclear boundaries. A diagram that tries to cover everything ends up describing nothing clearly. When you scope your process correctly, you\u2019re not limiting depth\u2014you\u2019re increasing clarity.<\/p>\n<p>This chapter guides you through setting realistic, actionable BPMN modeling scope. You\u2019ll learn how to define process boundaries, choose the right abstraction level, and align your model with stakeholder needs. By the end, you\u2019ll build diagrams that tell a story, not a story of confusion.<\/p>\n<h2>Understanding BPMN Process Scope<\/h2>\n<p>BPMN process scope defines the start, end, and extent of a process model. It\u2019s not just a box\u2014it\u2019s a decision. Your model shouldn\u2019t include every task from every department. It should focus on one workflow, from beginning to end.<\/p>\n<p>Consider a loan approval process. The scope might begin when a customer submits an application and end when the decision is communicated. What happens before\u2014like credit checks\u2014may be relevant but not part of this model.<\/p>\n<p>Here\u2019s a truth: over-scoping turns a simple model into a tangled mess. Under-scoping, on the other hand, leaves critical decisions out. The goal is precision, not completeness.<\/p>\n<h3>Why Scope Matters in Real-World Modeling<\/h3>\n<p>When I first worked with a team on an invoice processing model, they included every task from procurement, accounting, and legal. The diagram had 72 elements and no one could explain it. After re-scoping to focus only on the approval and issuance phase, the model shrank to 14 elements\u2014still accurate, now understandable.<\/p>\n<p>The scope determines who reads the model. A developer needs a different level of detail than a vendor or a manager. A well-scoped model answers: What am I trying to solve? Who will use this?<\/p>\n<p>Use this simple checklist to assess your scope:<\/p>\n<ul>\n<li>Does the start event clearly mark the beginning of the modeled workflow?<\/li>\n<li>Does the end event represent a meaningful outcome?<\/li>\n<li>Are all elements within the scope relevant to this specific process?<\/li>\n<li>Would a stakeholder understand this model without extra context?<\/li>\n<\/ul>\n<h2>Defining Process Boundaries with Clarity<\/h2>\n<p>Process boundary definition is not a formality. It\u2019s the foundation of a usable model. Without it, your process becomes ambiguous\u2014even if all symbols are correct.<\/p>\n<p>Start with a clear statement: \u201cThis model shows the steps a user takes to submit a support ticket.\u201d That\u2019s your boundary. Everything outside\u2014like how the ticket is prioritized or assigned\u2014is out of scope.<\/p>\n<p>Use the <strong>boundary definition checklist<\/strong>:<\/p>\n<ol>\n<li>Identify the trigger event that starts the process.<\/li>\n<li>Define the final outcome the model must achieve.<\/li>\n<li>List all elements that are part of this workflow.<\/li>\n<li>Clearly exclude tasks, roles, or systems that belong to other processes.<\/li>\n<\/ol>\n<p>For example, in a customer onboarding process, the boundary starts with \u201ccustomer completes registration\u201d and ends when \u201caccess is granted.\u201d Tasks like \u201cverify ID documents\u201d and \u201cconfigure user permissions\u201d are in scope. \u201cSend welcome email\u201d may be in scope if it\u2019s part of onboarding. But \u201cmonitor login activity\u201d belongs in another model.<\/p>\n<h3>Boundary Definition in Practice<\/h3>\n<p>Let\u2019s walk through a real example. You\u2019re modeling the \u201cCreate New User\u201d workflow in an HR system. The scope includes:<\/p>\n<ul>\n<li>HR submits user data<\/li>\n<li>System generates login credentials<\/li>\n<li>HR sends notification to the new user<\/li>\n<li>First login is recorded<\/li>\n<\/ul>\n<p>Excluded:<\/p>\n<ul>\n<li>How passwords are encrypted<\/li>\n<li>How user roles are assigned post-login<\/li>\n<li>How security audits are triggered<\/li>\n<\/ul>\n<p>Now, the model is focused, readable, and serves its intended purpose.<\/p>\n<h2>Choosing the Right Abstraction Level<\/h2>\n<p>Abstraction level determines how much detail to include. Too much detail overwhelms. Too little misses critical decisions.<\/p>\n<p>There\u2019s no universal level\u2014only the one that fits the audience. A high-level model for executives might show only three steps: \u201cSubmit Request,\u201d \u201cReview Approval,\u201d \u201cExecute Action.\u201d A developer needs to see each task, decision point, and system interaction.<\/p>\n<p>Consider this table for guidance:<\/p>\n<table>\n<tbody>\n<tr>\n<th>Abstraction Level<\/th>\n<th>Best For<\/th>\n<th>Example<\/th>\n<\/tr>\n<tr>\n<td>High-level<\/td>\n<td>Executives, stakeholders<\/td>\n<td>\u201cApproval Request Sent\u201d \u2192 \u201cDecision Made\u201d \u2192 \u201cAction Taken\u201d<\/td>\n<\/tr>\n<tr>\n<td>Mid-level<\/td>\n<td>Business analysts, managers<\/td>\n<td>\u201cReview application\u201d \u2192 \u201cVerify documents\u201d \u2192 \u201cApprove or reject\u201d<\/td>\n<\/tr>\n<tr>\n<td>Low-level<\/td>\n<td>Developers, automation teams<\/td>\n<td>\u201cCall API \/get-document-status\u201d \u2192 \u201cCheck if document is valid\u201d \u2192 \u201cReturn status to user\u201d<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Always match the abstraction level to the purpose. A model meant for training shouldn\u2019t include technical service calls. A model for automation must.<\/p>\n<p>Here\u2019s a rule I\u2019ve used for years: if you\u2019re not sure whether a task belongs, ask: \u201cWould removing this make the model less useful for my target audience?\u201d If yes, keep it. If no, cut it.<\/p>\n<h3>Avoiding Common Abstraction Pitfalls<\/h3>\n<p>One pattern I see often: modeling every screen in a software workflow. This isn\u2019t about process\u2014this is about UI design. A BPMN model should not show \u201cclick \u2018Save\u2019 button\u201d as a task. Instead, model \u201cSave application data\u201d as a single task.<\/p>\n<p>Another pitfall: merging multiple processes into one. Imagine combining \u201cemployee onboarding\u201d and \u201cequipment provisioning.\u201d They\u2019re related, but the scope should remain separate unless you\u2019re modeling a collaboration.<\/p>\n<p>Ask yourself: \u201cIs this task necessary for the process flow, or is it a detail that distracts?\u201d If it\u2019s the latter, it doesn\u2019t belong in the core model.<\/p>\n<h2>How to Test Your Process Scope<\/h2>\n<p>After defining scope and abstraction level, test your model with two simple questions:<\/p>\n<ol>\n<li>Can someone unfamiliar with the process understand the workflow in under 2 minutes?<\/li>\n<li>Would removing any task break the logical flow or change the outcome?<\/li>\n<\/ol>\n<p>If the answer to either is \u201cno,\u201d revisit your scope.<\/p>\n<p>I once worked on a process where a team insisted on including a \u201cmanual data entry\u201d task. But the data was already in a system\u2014no manual input. Removing it simplified the flow and removed a source of error.<\/p>\n<p>Use this <strong>scope validation checklist<\/strong>:<\/p>\n<ul>\n<li>Each task directly contributes to the final outcome.<\/li>\n<li>No task is duplicated across multiple models without a clear reason.<\/li>\n<li>Every gateways and decisions are necessary for flow control.<\/li>\n<li>System tasks are only included if they impact the process outcome.<\/li>\n<\/ul>\n<p>When you can answer \u201cyes\u201d to all, your model is ready to share.<\/p>\n<h2>Final Thoughts: Keep It Simple, Keep It Clear<\/h2>\n<p>BPMN process scope isn\u2019t about what you can draw. It\u2019s about what you should draw. A good model is not defined by how many elements it has, but by how clearly it communicates.<\/p>\n<p>Remember: you\u2019re not building a map of every road in a city. You\u2019re showing one route from point A to point B. The rest can be ignored.<\/p>\n<p>With a well-defined scope, you\u2019re not just drawing a diagram\u2014you\u2019re telling a story that others can act on. And that\u2019s the real power of BPMN.<\/p>\n<h2>Frequently Asked Questions<\/h2>\n<h3>What happens if I don\u2019t define the process boundary?<\/h3>\n<p>Without a clear boundary, your model becomes ambiguous. Stakeholders may interpret the flow differently, leading to misunderstandings, rework, or incorrect automation.<\/p>\n<h3>How do I decide the right abstraction level for my model?<\/h3>\n<p>Ask: who will use this model? If it\u2019s for executives, keep it high-level. For developers, include system interactions. Match detail to audience needs.<\/p>\n<h3>Can a BPMN process include tasks from multiple departments?<\/h3>\n<p>Yes\u2014but only if they belong to the same workflow. For example, a customer onboarding process may involve HR, IT, and sales. But each role\u2019s tasks should be in the correct lane or sub-process.<\/p>\n<h3>Should I model every decision point in my process?<\/h3>\n<p>Only if it affects the outcome. If a decision is internal or doesn\u2019t alter the flow, it may be better omitted. Focus on decisions that change the path.<\/p>\n<h3>What\u2019s the difference between BPMN modeling scope and BPMN abstraction level?<\/h3>\n<p>Scope defines what\u2019s included or excluded from the model. Abstraction level determines how much detail to show. One defines boundaries; the other defines depth.<\/p>\n<h3>How can I improve my process model if it\u2019s too complex?<\/h3>\n<p>Start by asking: \u201cWhat\u2019s the one thing this model must show?\u201d Then remove tasks that don\u2019t directly contribute. Use sub-processes or swimlanes to organize complexity.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Many beginners confuse BPMN modeling scope with the entire business process. That\u2019s a common misstep. The process scope isn\u2019t about capturing every detail\u2014it\u2019s about defining what\u2019s included and what\u2019s not. Think of it as drawing a boundary around a conversation: not every side discussion belongs in the main flow. I\u2019ve seen models fail not from [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":402,"menu_order":0,"template":"","meta":{"_acf_changed":false,"inline_featured_image":false,"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"default","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-4)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"doc_tag":[],"class_list":["post-403","docs","type-docs","status-publish","hentry"],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>BPMN Process Scope: Define Your Model\u2019s Boundaries<\/title>\n<meta name=\"description\" content=\"Learn how to define BPMN process scope, boundary definition, and abstraction level to create clear, focused process models that communicate effectively across teams and systems.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/\" \/>\n<meta property=\"og:locale\" content=\"fr_FR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"BPMN Process Scope: Define Your Model\u2019s Boundaries\" \/>\n<meta property=\"og:description\" content=\"Learn how to define BPMN process scope, boundary definition, and abstraction level to create clear, focused process models that communicate effectively across teams and systems.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/\" \/>\n<meta property=\"og:site_name\" content=\"Visual Paradigm Skills Fran\u00e7ais\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Dur\u00e9e de lecture estim\u00e9e\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/\",\"name\":\"BPMN Process Scope: Define Your Model\u2019s Boundaries\",\"isPartOf\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\"},\"datePublished\":\"2026-02-25T10:17:25+00:00\",\"description\":\"Learn how to define BPMN process scope, boundary definition, and abstraction level to create clear, focused process models that communicate effectively across teams and systems.\",\"breadcrumb\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/#breadcrumb\"},\"inLanguage\":\"fr-FR\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"BPMN Fundamentals for Beginners\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/\"},{\"@type\":\"ListItem\",\"position\":3,\"name\":\"Building Realistic Process Models\",\"item\":\"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/\"},{\"@type\":\"ListItem\",\"position\":4,\"name\":\"Scoping Your Process Models Effectively\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#website\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"fr-FR\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#organization\",\"name\":\"Visual Paradigm Skills Fran\u00e7ais\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"fr-FR\",\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"contentUrl\":\"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg\",\"width\":70,\"height\":70,\"caption\":\"Visual Paradigm Skills Fran\u00e7ais\"},\"image\":{\"@id\":\"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/\"}}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"BPMN Process Scope: Define Your Model\u2019s Boundaries","description":"Learn how to define BPMN process scope, boundary definition, and abstraction level to create clear, focused process models that communicate effectively across teams and systems.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/","og_locale":"fr_FR","og_type":"article","og_title":"BPMN Process Scope: Define Your Model\u2019s Boundaries","og_description":"Learn how to define BPMN process scope, boundary definition, and abstraction level to create clear, focused process models that communicate effectively across teams and systems.","og_url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/","og_site_name":"Visual Paradigm Skills Fran\u00e7ais","twitter_card":"summary_large_image","twitter_misc":{"Dur\u00e9e de lecture estim\u00e9e":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/","name":"BPMN Process Scope: Define Your Model\u2019s Boundaries","isPartOf":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website"},"datePublished":"2026-02-25T10:17:25+00:00","description":"Learn how to define BPMN process scope, boundary definition, and abstraction level to create clear, focused process models that communicate effectively across teams and systems.","breadcrumb":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/#breadcrumb"},"inLanguage":"fr-FR","potentialAction":[{"@type":"ReadAction","target":["https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/bpmn-process-scope-effective-modelling\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/skills.visual-paradigm.com\/fr\/"},{"@type":"ListItem","position":2,"name":"BPMN Fundamentals for Beginners","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/"},{"@type":"ListItem","position":3,"name":"Building Realistic Process Models","item":"https:\/\/skills.visual-paradigm.com\/fr\/docs\/bpmn-fundamentals-for-beginners\/bpmn-process-modeling\/"},{"@type":"ListItem","position":4,"name":"Scoping Your Process Models Effectively"}]},{"@type":"WebSite","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#website","url":"https:\/\/skills.visual-paradigm.com\/fr\/","name":"Visual Paradigm Skills Fran\u00e7ais","description":"","publisher":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/skills.visual-paradigm.com\/fr\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"fr-FR"},{"@type":"Organization","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#organization","name":"Visual Paradigm Skills Fran\u00e7ais","url":"https:\/\/skills.visual-paradigm.com\/fr\/","logo":{"@type":"ImageObject","inLanguage":"fr-FR","@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/","url":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","contentUrl":"https:\/\/skills.visual-paradigm.com\/fr\/wp-content\/uploads\/sites\/6\/2026\/02\/favicon.svg","width":70,"height":70,"caption":"Visual Paradigm Skills Fran\u00e7ais"},"image":{"@id":"https:\/\/skills.visual-paradigm.com\/fr\/#\/schema\/logo\/image\/"}}]}},"_links":{"self":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/403","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs"}],"about":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/types\/docs"}],"author":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":0,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/403\/revisions"}],"up":[{"embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/docs\/402"}],"wp:attachment":[{"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/media?parent=403"}],"wp:term":[{"taxonomy":"doc_tag","embeddable":true,"href":"https:\/\/skills.visual-paradigm.com\/fr\/wp-json\/wp\/v2\/doc_tag?post=403"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}