I created an SPFX application with the Teams Toolkit that utilises Microsoft Graph API to get data,after packaging and deploying the manifest folder to Teams Admin Center, it renders well with accounts that have Teams Admin and Global Admin access but accounts without this access are unable to access the application as it shows an error as seen in the image.
The Component ID and version in the message are speaking to the React-dom component id and version in the project.
Please i need suggestions on how to resolve this as i am not sure if its just a permission issue
I have tried updating my spfx version but that didnt work as i was already working with the required version of spfx and all other dependency versions
You can raise an issue in https://github.com/OfficeDev/TeamsFx/issues so we can support you better.
I tried to reproduce your issue but failed. The web part displays successfully for account without Teams/Global Admin in my side. Let's clarify the steps before the issue happens:
Create a SPFx project in Teams Toolkit and utilizes Microsoft
Graph API to get data
Click 'Provision in the cloud' to provision
the Teams app (with Teams/Global admin account)
Click 'Deploy to
the cloud' to generate the sppkg and deploy it to SharePoint (with
Teams/Global admin account)
Click 'Publish to Teams' to publish
the Teams app manifest in Teams app catalog (with Teams/Global admin
account)
Approve the submission in Teams admin portal
Install
and open the Teams App in Teams with Teams/Global admin account and
the web part displayed successfully
Install and open the Teams
App in Teams without Teams/Global admin account and the web part
shows error.
Could you help confirm whether you're having the steps above to reproduce the issue?
BTW, after deploying you should be able to use the web part with normal account in regular page in SharePoint. Maybe you can check whether everything is OK in SharePoint app catalog
SPFx solution after deploy to SP app catalog
Do we have API for Organisation Settings (Administrative settings) -> Security Settings for Slack ?
Slack does not have an API to manage Org-wide settings at this time.
I have created a Teams App with the App Studio. When I install it with App Studio everything is working? I am now trying to publish the app to the tenant app store
I have downloaded the app packaged from App Studio and uploaded the package to the Teams admin portal. The package uploads without any errors and the app is shown in the catalog list as a custom app
I have enabled
“Allow third party app”,” Allow any new third party apps… ” “Allow interaction with custom apps” on ”org-wide app” settings
-the global Permission policy I have “Allow all apps” on the three subjects
-the Global Setup Policy I have “Upload custom apps” and ”Allow user pinning” on
But my app does not show in the catalogue in the Teams client
After adding and removing the same police, restarting the client multiple times and waiting 48 hours- The app now show up in the catalog
I have 2 teams in my VSTS Project: Administrators and Developers.
I need to deny access to the Administrator Backlog to users inside of Developers.
Now any user has access to all teams backlogs and I can't find how to restrict this.
Anybody can help me?
Thanks!
The answer here works, but what do you do when you get 5 teams? 100 teams? For each team, do you Deny permissions to the other 99? Not very scalable. So I tried to find another way and figured out what I think is a better approach.
My goal, btw, was to create a good user-experience for my stakeholders, and constrain what they are able to access and modify. I personally feel that the members of the software engineering team should have access to and be able to contribute to any team... but that's personal opinion.
I got flummoxed, at first, by the fact that teams, when created, get added to Contributors... giving them access to all areas. So first, remove the Team security group from the Contributors group. Second, set the "View project-level information" permission to "Allow" for the team. Last, edit security for the top-level Area associated with the team (sub-areas inherit permissions), add the team group to security for that Area, and "Allow" the following for the team group
Edit work items in this node
View work items in this node
Manage test plans (if we want end-users involved in UAT work within Azure DevOps)
Manage test suites (same)
This assumes, btw, that you've also assigned the top-level Area for that group to that team, and included sub-areas.
At this point, as a member of a team, a stakeholder will only see the teams they are members of, under "My Teams", when viewing boards, backlogs, and sprints. They could go out of their way to browse any other board... but they wouldn't see anything because they don't have permissions to the items on those boards.
Then, I would assign the various stakeholders to the team(s) in which they had a stake.
One could also add software engineering members to teams as well, as this uses an "Allow" approach instead of a "Deny" approach, and so their "My Teams" list would include teams they were members of. Personally, I'd probably go with allowing the engineers to control it themselves through "favorites", rather than having to administer adding \ removing engineers from team security groups.
You can restrict the team users with Area Security.
Follow below steps to achieve that:
Create 2 Groups for the 2 teams: (Admin -> Security -> Create Group)
e.g.: AdminGP for Administrators team, DevGP for Developers
team.
Add the team users to the corresponding Group.
Navigate to Home project, then create Areas for each Team if no
areas created before. (Admin -> Work -> Areas)
e.g. TeamAdmin and TeamDev in below screenshot
Navigate to the specific Team, and set the default Area path for
the team.
Back to home project, Admin -> Work -> Areas, Right click the
AdminGP area -> Security
Add the corresponding Groups for the teams, then set bellow
permissions for TeamDev Group (Developers team):
View permissions for this node - Deny
View work items in this node - Deny
Thus the members in Developers team cannot see the Administrators team's work items in Backlog/Board.
I am using a Magento website with over 10 stores. These stores are managed by different companies. However, if a customer created an account in Store(View) 1, he can also log in on StoreView 2. Is their a way to restrict this and make sure he can only login to the Store he was created in?
I know it is possible to restrict account sharing on a website level, but I need Store level.
Thanks!
By default, Magento only supports limiting user accounts on a Global or per Website basis, not per Store.
Those settings are at Admin > System > Configuration > Customers > Customer Configuration > Account Sharing Options.
To try to answer your question, you can force the user to logout between stores/websites. Look in Admin > System > Configuration > General > Web > Session Validation Settings and set Use SID on Frontend to No.
If the limitations have to be per Store, then you will need a module to introduce that.