Criteria	Usage
Questions with keyword1 or keyword2	keyword1 keyword2
Questions with a mandatory word, e.g. keyword2	keyword1 +keyword2
Questions excluding a word, e.g. keyword2	keyword1 -keyword2
Questions with a specific tag and keyword(s)	+[tag1] keyword1
Questions with two or more specific tags and keyword(s)	+[tag1] +[tag2] keyword1
To search for all posts by a user or all posts with a specific tag, start typing and choose from the suggestion list.

George Rainovic suggested an idea (#2204) · Nov 13, 2017 at 05:13 PM · blueprint user permissions sandbox ideas

Sharing blueprint/sandbox with a team/community

Currently, the blueprint can be private or public, there is nothing in-between.

Is there any plans to share the blueprint with a selected group of people (team/community) that is smaller than ‘public’?

We've seen this request coming from people who want to share, but they do not feel comfortable sharing with everyone.

*** Idea ***

The team/community could have one or more users. It can have a moderator/owner who can manage membership in the team/community – adding/removing users. We do not need administrators to manage this aspect of the system.

***

Maybe the team/community membership can be used to control access to the sandboxes, too. In that case, team/community could be added to ‘Permitted users’ by the sandbox owner.

The user, member of the team/community, should meet the other user access rules to be allowed to control the sandbox. The team/community feature is not to replace other access control mechanisms.

***

The first choice for the right word will be a ‘group’, but groups are already used in Quali for associating users to domains.

Maya Ber commented · Nov 13, 2017 at 06:23 PM

Hi @grainovic. Thanks for the idea. Blueprint access control is addressed by domains, and it's not in our current plans to add another level of control and permissions under the Domain. Would it make sense for you to add domains for certain communities? Another option, if you would like to make users feel more comfortable about sharing, and permission is less of an issue here, would be to use blueprint categories to categorize such blueprints as "beta" or "sneak peek". Look forward to know what you think.

George Rainovic commented · Nov 13, 2017 at 06:46 PM

Hi Maya,

Categories do not solve the problem for some of my users. They just do not want to share with the public, they want to share with selected people.

Potentially, in our case, this means tens of new domains. We do not want to add that many new domains, b/c we need to add resources to all new domains.

Maya Ber commented · Nov 15, 2017 at 04:18 PM

Hi @grainovic. I'm not sure managing tens of communities would be a lower overhead.. Perhaps it would make sense to invest in making domain management easier (e.g. copy domain)? BTW, in our internal implementations of Cloudshell we use domains to make similar separation.

0 · Show 1

George Rainovic · Nov 15, 2017 at 06:58 PM 0

Besides creating team/community, admins do not need to manage them if the team/community has a moderator/owner.

---

When a new resource is added, we need to add it to all those domains. It is easy to miss something.

Admins see all those domains in the list - hard to navigate. I want to avoid that clutter.

Public sharing blueprint with all those domains is hard (impossible) because boundaries between domains are hard.

Yaniv Kalsky commented · Nov 15, 2017 at 05:46 PM

Hi @grainovic

Can you also elaborate on the users' concerns about having the blueprints public to all?

Yaniv

0 · Show 1

George Rainovic · Nov 15, 2017 at 06:40 PM 0

In my case, it could be called a 'multi-tenant' environment. Not all of our users belong to the same company (for example our partners use it).

Marcelino Chua commented · Mar 09, 2018 at 02:52 PM

I'd like to bring this up again - since we just got pinged (again) by our customer(tenant) for this requirement. I have a feeling this will keep coming up.

Background: We are providing our system (equipment, automation, etc.) as a platform our tenants (customers). This tenant, in turn has their own customers. Each of their customers want to share their blueprints with folks in the same company - but do NOT want anyone in another company to see what they've created.

This tenant currently has their own domain and they have a domain administrator.

Trying to create a new domain for each of their customers would be a big burden on the platform sysadmins... it SHOULD be possible for the domain administrator to create their own sub-domains and assign the users in their domain to the appropriate sub-domain.

Announcements >
CloudShell >	TestShell >
Developers >	BI (Business Inteligence) >

CloudShell's Dev Guide >	Configuration Management >
Getting started with Shells >	Extending CloudShell with Cloud Providers >
Getting started with Orchestration >	API Guide >

Announcements
CloudShell	TestShell
Developers	BI (Business Inteligence)

CloudShell's Dev Guide	Configuration Management
Getting started with Shells	Extending CloudShell with Cloud Providers
Getting started with Orchestration	API Guide

Welcome to Quali's Community Forums!

Quali's Idea Box!

Quali's Community Integrations

Sharing blueprint/sandbox with a team/community

5 comments

Welcome to Quali's Community Forums!

Welcome to Quali's Idea Box!

Quali's Community Integrations

Your Opinion Counts

Follow This Idea

Related Ideas