Skinbase.org

Studio help

Studio is the creative control center of Skinbase.

Use Studio to manage drafts, uploads, publishing, artworks, cards, collections, and collaborative work before and after it goes public. This page explains how Studio fits into the platform, how personal and Group contexts differ, and how to use the workspace without creating avoidable confusion.

Core purpose
Private creative workspace

Studio is where you prepare, organize, review, and manage work before and after it goes public.

Common confusion
Context changes behavior

Personal Studio and Group Studio can expose different actions because ownership and permissions are different.

Golden rule
Check context before publish

Publishing from the wrong context is one of the easiest ways to create avoidable confusion.

Foundations

What Studio is

Studio is the private management workspace for creators. Public pages show published work. Studio is where you prepare, organize, edit, review, and manage that work before and after it reaches the public side of Skinbase.

Studio is private

Studio is not your public profile. It is the working area where creator actions happen, drafts live, and management choices are made.

Public pages are the result

The public side of Skinbase is what people see after you publish. Studio is where you shape that result intentionally.

Context

Personal Studio vs Group Studio

This is one of the most important parts of Studio. The active context changes ownership, available actions, and who is allowed to do what.

Comparison between Personal Studio and Group Studio
TopicPersonal StudioGroup Studio
Who the work belongs toYour own drafts, uploads, cards, collections, and creator activity.Work owned, published, or coordinated under a Group identity.
Why actions differYou usually control the full flow for your own content.Available actions depend on Group role, trust level, and review workflow.
Publishing contextPublishes under your personal creator identity.Publishes under the Group identity while preserving individual credit.
Where drafts liveIn your personal Studio draft and content views.Inside the Group context, often with shared review or approval behavior.
Coordination styleBest for solo publishing and direct control.Best for shared publishing, collaboration, reviews, member management, and structured releases.

Workspace map

Main Studio areas

Studio already includes a broad set of creator surfaces. You do not need to memorize every route, but it helps to understand the main areas and what each one is for.

Dashboard and content views

Use the main Studio dashboard, content view, and analytics surfaces to see what is active, what is scheduled, and what still needs attention.

Artworks and drafts

Artworks, drafts, scheduled items, calendar views, and archived work all live inside the management side of Studio rather than on public profile pages.

Cards and collections

Cards and collections are managed as creative tools inside Studio, where you can build, organize, and refine them before people see the result publicly.

Groups and collaboration

When collaboration is involved, Group Studio adds shared publishing, member management, review flows, projects, releases, challenges, events, assets, and related operations.

Settings and preferences

Studio also includes settings, preferences, profile-facing tools, activity, and creator operations that do not belong on the public side of Skinbase.

Future-ready workflow surface

The current Studio already covers many creator operations, and the help page is written to stay useful as more modules grow into the workspace over time.

Workflow

Drafts and publishing

Drafts are unfinished workspace items. Publishing is the moment work becomes public. Treat those as different stages with different responsibilities.

  1. 1

    Start work in the right context

    Before you upload, edit, or publish, confirm whether the work belongs to your personal Studio or to a Group context.

  2. 2

    Treat drafts as unfinished workspace items

    Drafts are where unfinished work lives while you are still checking metadata, previews, contributor credit, timing, or overall quality.

  3. 3

    Review metadata before publishing

    Titles, descriptions, tags, categories, previews, context, and contributor information should be reviewed before the final publish step.

  4. 4

    Use review when collaboration needs it

    Group workflows may put work into review before publish so trusted members can check context, quality, and credit.

  5. 5

    Publish only when the public version is ready

    Do not treat publish as a draft save button. Publish when the work is accurate, presentable, and in the right place.

Content

Managing artworks

Studio is where artwork workflows happen: upload, draft review, metadata cleanup, preview checks, updates, and final publishing decisions.

Create or upload the work into the correct Studio context first.
Review title, description, and public-facing metadata before publish.
Check tags, categories, and preview quality so the public version lands clearly.
Make sure contributor credit reflects who authored, uploaded, and contributed to the work.
Update published work intentionally instead of letting metadata drift over time.

Creative tools

Managing cards and collections

Cards and collections are part of the creative management side of Studio. They are not only public-facing features; they also live inside the workspace where you build and organize them.

Cards

Use Studio for card creation, remixing, editing, previews, and analytics. Cards are part of your creative workflow, not just a public gallery surface.

Collections

Use Studio to organize groups of work, shape presentation, and manage curated content as a creative management task rather than an afterthought.

Advanced workflows

Projects, releases, and other advanced modules

As workflows become more collaborative or structured, Studio extends beyond simple drafts and publishes into richer operating surfaces.

Projects help teams organize structured collaboration, milestones, and linked work.
Releases package a larger publication moment into a clearer shared launch surface.
Challenges, events, and assets extend Studio into themed collaboration, timed publishing, and shared resources.
Group review queues, invitations, and join requests add operational structure when collaboration grows beyond simple direct publishing.

Habits

Best practices

Good Studio habits reduce confusion, keep work organized, and make publishing smoother for both solo creators and teams.

Review drafts regularly so Studio stays usable instead of turning into a backlog graveyard.
Keep personal and Group work clearly separated so ownership stays obvious.
Publish only after metadata, previews, and contributor credit are truly ready.
Use advanced modules only when they solve a real workflow problem.
Treat Studio like a workspace for preparation and management, not as a public profile page.
Keep contributor records accurate so teams avoid confusion later.

Avoid this

Common mistakes

Most Studio confusion does not come from the existence of many tools. It comes from using the right tool in the wrong context or skipping basic review steps.

Publishing under the wrong context because the active Studio scope was not checked first.
Leaving metadata half-finished and hoping to clean it up after the work is public.
Forgetting to verify contributor credit before a collaborative publish.
Treating Studio like a public page instead of a private working area.
Giving too many Group members too much access when a smaller permission set would be safer.
Ignoring drafts until lists become cluttered and hard to maintain.

FAQ

Studio FAQ

These fast answers cover the questions that come up most often when people are new to Studio or switching into collaborative workflows.

Studio is the private creator workspace on Skinbase. It is where you manage drafts, uploads, publishing, cards, collections, settings, and other operational parts of your creative work.

Troubleshooting

Troubleshooting

Use these shortcuts when Studio feels confusing, empty, or inconsistent. Most issues come down to context, filters, or permissions.