Build and govern a marketplace skill
Plan and review a Marketplace Skill Builder submission using least privilege, explicit data boundaries, and tenant governance.
Audience, roles, and scope
Portal Skill Builder interface and governance considerations; it is not a general public API or SDK contract.
Who this is for
- Authorized skill designers
- Tenant reviewers
Roles
- Skill author
- Security reviewer
- Marketplace administrator
Before you begin
- Tenant authorization to design a skill
- A documented owner, purpose, data classification, and review path
Article tags
- skill-builder
- marketplace
- integration
- governance
- developer
Procedures
Follow the sequence and stop when identity, authorization, target, or result differs from the article.
Prepare a governed skill definition
Define the smallest defensible capability before any publication request.
- 1Define purpose and ownership
Document the business task, accountable owner, intended users, publisher identity, and support lifecycle.
- 2Minimize access and data
Specify only required systems, actions, fields, retention, and tenant scope; exclude secrets from descriptions and examples.
- 3Submit for independent review
Validate test evidence, failure behavior, privacy and security controls, then use the configured review path before release.
The skill definition is reviewable, least-privileged, and not represented as production-approved before governance completes.
Security and data handling
- Use only the identity, tenant, role, and data scope approved for the task.
- Verify targets and expected effects before saving, sending, publishing, exporting, deleting, or approving.
- Keep secrets and regulated data out of screenshots, URLs, free-text diagnostics, and ordinary support messages.
- Separate author and approver duties for high-impact or sensitive skills.
- Rotate or revoke integration credentials through the owning system; never embed them in builder text.
Known limitations
- The Skill Builder is a beta interface and may represent preview or deployment-specific workflow.
- No public API versions, rate limits, SDK guarantees, or automatic production publication are asserted by this article.
Troubleshooting
You cannot open Vianordis Portal
Likely cause: The session expired, the account is not entitled, or the required tenant or role claim is missing.
- Open the service through the approved Vianordis entry point and sign in again.
- Confirm the intended organization, tenant, and account are in use.
- If access remains denied, record the time and request an entitlement check; do not attempt direct-URL bypasses.
A documented control or navigation item is not visible
Likely cause: The current role, subscription, tenant configuration, release status, or feature flag does not expose it.
- Confirm the audience, role, prerequisites, and limitations in this article.
- Refresh after a new sign-in and verify the correct tenant context.
- Ask the responsible administrator whether the capability is enabled before reporting a defect.
A saved change or background result is not visible
Likely cause: Validation failed, processing is incomplete, the view is stale, or the feature is locally simulated rather than persisted.
- Review inline validation, status indicators, filters, and the selected tenant or workspace.
- Refresh once and search by a stable identifier before repeating the action.
- Do not repeat irreversible or externally visible actions until the first operation's state is known.
Source verification
Skill Builder fields and workflow were reviewed in source; runtime publication and integration guarantees are deployment-dependent.
Reviewed paths at e7035d9
src/app/(portal)/marketplace/builder/page.tsxsrc/components/marketplace/SkillBuilder.tsxsrc/app/api/marketplace/builder/route.tssrc/app/api/marketplace/builder/[skillId]/route.ts
Contact support
Contact support when
- A repeatable Vianordis Portal error blocks an approved task
- Expected access, tenant scope, data, or status appears incorrect
- A security, privacy, financial, compliance, or data-loss concern is suspected
Include
- The page, action, expected result, and exact error text
- The time of occurrence with time zone and whether it is reproducible
- Your tenant, role, browser, and sanitized record or correlation identifier
- The troubleshooting steps already completed
Never include
- Passwords, access tokens, API keys, recovery codes, session cookies, or private keys
- Unredacted personal, financial, health, student, employee, or other regulated data
- Confidential documents or message bodies unless support provides an approved secure channel