Hey @bram.moreinis , thanks for your question!

Unfortunately there is not a specific flow or process to do what you want to do other than doing it manually. For instructions on creating teams, adding users to the teams, and adding documents to the teams (questions 1-4), check out our Use team hubs in Lucid to collaborate and stay organized article in the Lucid Help Center.

As for 5-6, team hubs may not actually be the best way to do this since any copy made of a document in a team hub is automatically placed in the team hub rather than in an individual’s documents folder. You would most likely be better off using a shared folder as described here (I know you’ve already seen this post, so I’m sorry it isn’t new information).

The reason for this is that team hubs are meant more for collaborative work, so typically the use case is housing documents that all members of the team are contributing to, rather than making a copy of.

Let me know if you have any additional questions!

Thank you, Morgan!

So, I was correct that I begin by adding users to teams. 

Team hubs are for team-wide collaboration, so if I’m only having student pairs (or triples) collaborate, I’m better served having them manually share documents with each other, or creating team hubs just for them if they’re going to be working together for a while on a project. 

Let me ask a few more:

1. If I want teams to see an array of template documents to work with but not edit, I can’t use a Team folder, since a Team Folder grants read/write access to everyone in the team and you can’t make it read-only, yes?
2. I don’t see a way to associate a team with a Team  Folder but change their access level.  I’m noticing now that I can pin Teams to the left sidebar for easy access - I should have students do that, too. I can’t do that for everyone as an admin, so that if they’re on a team they see it in the left sidebar, can I?  
3. I’m seeing that I could use a Team Space to display shapes linked to documents in a shared folder for students to access, although I’m still stuck with the fact that the whole team can write to it.  So unless I’m wanting a whiteboard full of stickies, I’m better off creating a LucidSpark for document access purposes, and giving read access. Yes?
4. If I want students to grab starter templates, fork them, and submit them, and there’s a sequence of these, I think could use a Kanban for the  Spark design, and this would have an added benefit of training the students in an aspect of Agile. 

Thank you for your answers! 

-Bram

PS: A while back, I added a comment to a thread about templates and folders where I thought it would make sense to share the template in a team folder.  I see now that I was wrong - because sharing in a team folder would make the templates editable.  However, nobody replied to me and now I can’t delete my comment there, so I’m afraid others will fall into that rabbit hole of mine.  Can you get someone to delete (or reply directly to) my comment so that doesn’t happen? 

Yes @bram.moreinis , your understanding sounds absolutely correct regarding smaller groups for team hub use.

For your questions:

1. You should actually be able to use a Team Folder for this. When you add collaborators to a Team Folder, you should have the option to make their permissions View only. You could also use a regular folder and share the folder with students.
2. Unfortunately no, you can’t automatically pin things to the side for students.
3. That sounds correct to me.
4. That sounds like an awesome idea, and I’d really love to see the execution of it if you decide to go that route.

Regarding your comment on the other post, I do believe it is possible to give collaborators view-only access to a Team Folder, so I think your comment is still okay. But if you still want me to delete it, let me know!

Thank you, @Morgan T .

 

I tried “Move to Team” with a blank folder and saw this scary message:
 

Now moved, it does not show a place to assign perms for the whole team, not that I see:

Although I can change perms as I add individuals from the team … so maybe that is the answer: one cannot assign team permissions as a group, but can do so individually. 

Is that right? I can’t say “Read only for team” but I can say “read only member by member”?  What is the default permission for a team folder -- full CRUD? 

Aha … I was APPARENTLY able to assign perms within a Team folder using Organizational Groups: 
 

So now I am wondering:  Were team members given CRUD (Create, Read, Update, Delete) access when I converted the folder to a team folder? And then. when I modified permissions using Org Groups, did those override the team-inherited perms?  If nobody knows, I will ask my students to test. 

I believe that is correct, but it would be the safest option to test with students to verify. Do you have any additional questions?

That should do it!  Hopefully this thread is a good record for others. Thanks so much, Morgan.