Have below two questions regarding how RCloud manages users and groups:
When users are initially provisioned to RCloud, is there a default group for all new users?
After creating a new group in RCloud, can I restrict only that group have access to my notebooks?
Sorry I missed your question for so long!
No, there is no default notebook permissions group.
There is no automatic way to assign your notebooks to a group.
As I'm sure you know, to assign a notebook to a group, click the i circle information icon next to the notebook, then click the link indicating the group it's currently in, and select the notebook group in the resulting dialog.
RCloud has always been about sharing techniques with others, so by default we want notebooks to be shared and searchable. However, we may consider a feature like this in the future.
Most likely it will be as an extension. I am not sure if the APIs exist to write such an extension today. (E.g. a hook when new notebooks are created.)
It may be possible to write a notebook today that moves all of your notebooks to a group.
Related
I have created a new Team/Area under our project within Azure DevOps.
When I send the URL for the backlog, the team members are able to access the link but not see any of the work items.
I have tried the following:
Confirm the user has Basic licence.
Confirm the user has access to the project.
Added the user to the Team for that area.
Is there anything obvious I am missing?
I am pretty confident this is not a bug, but just something in the process of giving users access that I am not doing.
Any help very much appreciated.
Thanks,
Alasdair.
When I send the URL for the backlog, the team members are able to access the link but not see any of the work items.
This could be caused by multiple reasons which means we might need to check several setttings.
Choose the right team in BackLogs page:
check the Project Settings-Team configuration-Areas, make sure the target Team area has been added:
Check Project Settings - Permissions and make sure your team has
the right permission to see the BackLogs Itmes.
Is this something that I need to set every time I create a new team?
No, you don't have to set them every time. When you create a team,
the Permissions setting could be automatically inherited:
Azure DevOps Services:
I need to hide all WIs belonging to one of the teams (= their Iteration Path) from the rest of the project.
Yet the team will need to see everyone else's WIs in this project
What is a proper way to achieve that?
set 'Deny' on 'View work items in this node' for all 'Contributors' and 'Readers'? But if my team is in 'Contributors' (so they can see all the other WIs) their access will also be denied (by inheritance), even if i add them explicitly.
Area Path 'Security' settings
I hoped to google a ready solution for such a common request, but have not found one yet, unfortunately.
But if my team is in 'Contributors' (so they can see all the other WIs) their access will also be denied (by inheritance), even if i add them explicitly.
This is actually an expected behavior which you can refer to Permission settings, it says For most groups and almost all permissions, Deny overrides Allow., this means when one of the team members is denied from View work items in this node in one group(such as his team) and allowed in another group(such as Contributors), he can't see the specific team's work items since the Deny overrides Allow.
It's also simple to understand logically, user A will be allowed to see another team's work items when his team is denied from?
My opinion is that you should move the user A to another team which could see the work items in the specific team.
If I create a new project and select the Agile process, my user stories will be grouped in iterations Eg "MyProject/Iteration 1".
However, If I create the project using Basic process and after the project has been created, changes the process to Agile I can group my user stories by Sprint Eg "MyProject/Sprint 1".
The latter is what I want, however as the process was set to Agile when the project was created (not by me), I'm trying to figure out how to change it to use Sprints as default?
Side note:
I cannot create a new project as I lack privileges
I cannot create a new process as I lack privileges
I cannot change to another process because I've already created a bunch or user stories
Although I can create sprints manually, I want it to be default.
Thank you!
From this document, we can know that iteration and sprints represent the same concept in the agile process.
Define Iteration Paths (aka sprints) and configure team iterations
So if you want to visually use Spirits as the default, you can add a new iteration named Spirit in team configuration, or change the name of the existing iteration to the Spirit style. Then set it as Default iteration. As shown in the following figure:
Because your current project is already Aglie process, the initial display must be MyProject/Iteration 1. If you want to display like MyProject/Sprint 1, you have to modify it later.
There are two ways to change the display: changing the process or manually modifying it.According to your Side note, obviously neither is feasible.
If you really want Spirits as default in agile progress project without any manual modification,you could submit a feature request in our Develop Community site. Our PM and product team will kindly review your suggestion.
There is no way to do this without changing the Process of your project.
I want to reorganize my variable groups in Azure DevOps, but before I delete any variable groups I want to make sure they are not used anymore. Also I need to link the newly created groups to old releases.
I could go over all release definitions and check which definition is linked to which variable groups, but there should be a more easy way for me show if a variable group still has linked releases. But I cannot seem to find that overview.
Is there an overview like above of will this be a pain in the ... to reorganize?
I don't see it available either, from the front-end or documented as available from the API. I think your only option is the one you mentioned to loop over the definitions to validate.
Looking at Task groups, they included a References tab which is probably what you want just on the Variable group. I'd recommend creating a feature request for this on the developer community.
Recently my firm acquired the Workiste solution (DMS) v9.3.2. It is connected to Outlook as a plugin.
To the left of Outlook, beneath the Inbox, Outbox, Deleted Items and other folders, there is a browser of this DMS, whose contracted label is FileSite.
Within FileSite there are the Documents in Checkout, Recent Documents and Recent Folders blocks.
Within the latter, there are all the 'workspaces' I've been getting via search.
However, many queries of these folder blocks (named 'workspaces') remain forever in the FileSite browser and therefore in Outlook.
I would like to keep only those 'workspaces' already searched and useful to me, those useful to my day-to-day, and not all those I search just take a peek, only.
The Worksite documentation is crappy on the web, so I did not find any information on how to clear the contents of the block called _Recent Folder (and if this is possible to do)
FileSite allows you to view recently accessed workspaces via the Recent Workspaces node. This is typically configured by you system administrator to show the last 10 or 20 workspaces that you accessed.
There is a corresponding My Workspaces node which will show you a list of workspaces that you are interested in, which may or may not be those same workspaces in your list of Recent Workspaces. To add to that list of My Workspaces simply right click any workspace (the reddish box icon that is the root of each workspace folder structure) and select Add to My Workspaces. Once you've done that a shortcut to that workspace will appear in your list of My Workspaces.
While the underlying workspace name typically won't be editable (usually because a company policy prohibits it) the shortcut is yours and you may rename it if you wish.
Also, in My Workspaces you may find that you want to logically group certain workspaces, perhaps because you're working on a set of related projects or matters. In that case you can right click on My Workspaces and select New..Category. A Category is merely a logical grouping of workspaces that is personal to you.
You can also make use of your My Favorites area to store shortcuts to workspaces and categorise them. The main difference between My Workspaces and My Favorites is that the latter allows you to add shortcuts to individual documents and even folders, not just workspaces.
In my experience, most people seem to find that My Workspaces gives them enough flexibility
Note that the My Workspaces and Recent Workspaces etc nodes are themselves configurable. That means your organization's administrator may have relabelled them, eg to My Matters and Recent Matters if you're a legal team, or My Projects and Recent Projects, etc. Also, you may have been restricted to only view certain nodes in FileSite
Your administrator or tech training team should be able to provide you with some comprehensive FileSite user guides that are produced by iManage in PDF format. Those guides provide much more detail