On SharePoint online, I have a document library which is created from MS Teams with the following folder hierarchy:
Library
==> Folder 1
==> Public SubFolder
==> Private SubFolder
What I want is when I grant access to Folder1 that the user gets access only to the public subfolder not to the private one.
What I tried:
I stopped inheritance on private subfolder
Then removed all permissions on the private subfolder
But then, if I add a user to Folder 1 (through manage access), he gets access to the private subfolder as well, which is something I need to prevent.
Any idea how to achieve this?
Regs
Related
I have an image hosting site set up in IIS, for example the products folder would be www.foobar.com/products/. Is this any way to prevent public access to this link, but allow public access to links such as www.foobar.com/products/some_product.jpg?
For some reason this folder doesn't return a 403 error, but the rest of the folders do. I don't see any differences in security settings under folder properties.
I want some mechanism, which will have a way to any git user to request access for private project
I can see a way where I (owner) can add any member to the project, But I want process where developers will request the access permission and I as owner will approve that instead of adding it manually
Is there any way?
It is possible to request access to a group or project. However, the group or project must be visible to the user (must be public or internal visibility).
Requesting access must also be enabled in the group or project settings.
You cannot request access to private groups or projects because you can't see them. For private visibility groups or projects, you can only be invited by existing members. However, you can have a private project inside of a public group (or subgroup). So you could make your group public and have users request access to the group (or subgroup) rather than the project directly.
Another alternative would be to have "permission" groups that have no projects. Have these groups public so users can request access. Then share access to the private project with that group.
Im trying access to site private page by site membership users
this is my step to do :
1-create a user
2-create user group and then add user to user group
3-create site (named testsite)
4-create private page in site (in step 3)
5-add usergroup(in step 2) to testsite (in step 3)
but after login with usergroup member show me "the requested resource was not found"
Liferay 7 public private convention
private
http://localhost:8080/group/{site name}/{private_page}
public
http://localhost:8080/web/{site name}/{private_page}
Try replacing group with web and see what you get
From a quick test that I've made, it seems to be a bug:
Create unprivileged user A
Create user group B
Make user A member of user group B
Make user group B member of Site C
Create a private page D in Site C
Log in as user A and try to navigate to D:
Result: Access Denied
Expected: Page D displayed.
I haven't checked https://issues.liferay.com for a known issue in this regard - you might want to do this and raise one in case you can't find it. Until fixed, you might need to find a workaround, e.g. script an individual site membership from the members of a usergroup. Luckily Liferay's API allows broad overrides on various levels - e.g. whenever membership to a usergroup (or site) changes, run additional code.
The question in brief: How can I set up WebDav so that unauthenticated users can download files with a URL, but can't access a list or make changes to the share?
The long version:
I'm new to WebDav. I'd like to replicate the Dropbox/public folder functionality. That allows any user with the correct URL to download a file, but no unauthenticated user can access a list of the files in the subdirectory or make any changes to the public folder.
I'd like to be able to send my client a URL to a file for download without exposing the whole contents of the share and, importantly, without requiring the client to have a user id and password.
The WebDav directory should also not be alterable or viewable by anyone who doesn't have a user id and password.
The WebDav directory is isolated on my server and I can alter .htaccess files.
I made a website in xpages.
The default access is No access and read public documents.
For content I have to mark in the security settings "Available to public access users"
but
I've put my sitemap.xml under the webcontent folder.
How can I make this sitemap available to for example Google ?
The file will be stored as a design Document in the database, accessible via NoteCollection. You'll probably need to do some trial and error to work out how to identify it, but you should then be able to set it as public access programmatically.
Alternatively, adding it as a File Resource will allow you to set it as public access via Domino Designer.
Another approach I've taken is to use a separate NSF for public access UI elements.