İçeriğe geç

Projects, folders & sharing

Bu içerik henüz dilinizde mevcut değil.

Adım 1/8

Her ürün burada başlar. Ürün ya da koleksiyon başına bir proje oluşturulur.

Projeler, klasörler ve paylaşım
Adım 1 / 8
  1. Her ürün burada başlar. Ürün ya da koleksiyon başına bir proje oluşturulur.
  2. Projeleri klasörlerde gruplayın. Klasörler kişiseldir, herkes yalnızca kendi klasörlerini görür.
  3. Shared with me, ekibinizin sizinle paylaştığı projeleri toplar.
  4. Erişim proje bazında belirlenir, toplu değil: devretmek istediğiniz kartın paylaş ikonunu açın. Diğer tüm projeler olduğu gibi kalır.
  5. Panel yalnızca o proje için açılır. İçindeki her ayar yalnızca bu projeye uygulanır.
  6. Share with team bu projeyi tüm üyeler için Workspace Projects’e koyar. Kapalı bırakırsanız, katalogunuzun geri kalanı ne yaparsa yapsın proje özel kalır.
  7. Doğrudan paylaşım projeyi belirli kişilere verir. Kişi yalnızca görüntüleyen viewer ya da ekip gibi çalışan editor olur.
  8. Current Access denetim kaydıdır: projeye kim sahip, kim verdi, ve rolü değiştirmek ya da geri almak tek tık.

Three lists cover every way a project can reach you:

  • My Projects: projects you own.
  • Workspace Projects: projects made visible to everyone in the workspace.
  • Shared with me: projects other people shared with you directly, possibly from other workspaces.

Access is decided per project, never in bulk. On the project card, the share icon opens the Manage Project Access panel, and everything in it applies to that one project. The rest of your catalogue is untouched, including projects in the same folder.

Inside the panel:

  1. Project Visibility → Share with team. Turn it on and this project appears in Workspace Projects for every member of the workspace. Leave it off and the project stays in your My Projects only. Save applies it.
  2. Direct Shares. Pick a workspace member, choose Viewer or Editor, and share. The project stays in your My Projects and shows up in that person’s Shared with me.
  3. Current Access lists who currently holds the project and who granted it, so a role can be changed or revoked later without guesswork.

Recipients are members of the project’s workspace. Direct sharing narrows access to specific members and cannot reach someone who isn’t on the team. To bring in somebody new, add them to the workspace first (see Team & workspaces).

Sharing is part of team collaboration and comes with the Professional and Enterprise plans. On Free, the panel offers the upgrade in place of the sharing controls. If a workspace moves to a plan without team collaboration, its existing shares and team visibility pause. Recipients no longer see or open those projects, and the owner still sees the shares under Current Access and can remove them. Everything resumes as it was once the plan is upgraded, so nothing has to be shared again.

The two mechanisms can be combined. A project that is not shared with the team can still be handed to two specific people, and a team-visible project can carry direct shares on top. This is useful when most of the team only needs to look, but two of them need to edit.

Those choices resolve to one of three states:

Level Effect
Private Only in your My Projects, unless you add a direct share.
Workspace Appears in Workspace Projects for every member of this workspace.
Direct share Stays in My Projects for you, and lands in the recipients’ Shared with me.

Direct shares and workspace visibility compose: a private project can still be shared with two specific teammates without opening it to the whole workspace.

Every direct share carries a role, chosen per person:

Role What the recipient can do
Viewer Open the project and its preview. Nothing is editable.
Editor Work on the project (models, scene, configurator) like the rest of the team. A model the live version uses is removed only by the project owner.

One condition sits on top of the role: an editor’s write access follows the workspace subscription. If the plan lapses, editors drop to read-only until it is active again. Worth checking against Plans & billing before an editor who “suddenly can’t save” is reported as a bug.

Shares are listed under Current Access with who granted them, and can be changed to the other role or removed at any time.

Publishing is separate from visibility. A project being visible to teammates says nothing about whether it is publicly reachable. See Publishing & sharing.

Folders organize the project lists:

  • Create folders, drag to reorder them, and delete them. Deleting a folder never deletes projects. They move back to the root.
  • Folders are personal. You see your own. They shape your lists and say nothing about who can open a project. Access is decided in Manage Project Access, above.
  • Move projects between folders any time (Move to Folder, where No folder means the root).
  • The folder and the list you’re browsing are part of the URL, so a bookmark or the Back button returns you to the same view. A folder link opens that folder for your account only.

Inside a project, click or drag a model file onto the upload area. Optimization and AR preparation run automatically. See Preparing models for formats and guidelines.