I have created an app inside getstream.io. I then added a team member but she does not seem able to see the app I created.
How do I ensure that team members can see the app and their secret key are viewable by fellow team members inside getstream.io?
Has the team member accepted the invitation (sent in an email)?
Related
When someone requests an access to a project in Azure DevOps(ADO), which usually happens when Project admins send a link to user via email or chat and they request for access by clicking on that link, we want the notification to add the user to organization should go to the org Admin and for the project it should go to the Project Admins.
Currently it is going to Project Collection Admins if the user is not in the ORG and no email is sent to the Project Admins. This is if the user tries to access the project through a link and is not added to the ORG.
Currently, the notifications only can be triggered when an user who has been invited into the Azure DevOps organization as a member does some operations in the organization.
If a user has not been invited into the organization, he cannot access the organization, cannot do anything in the organization, so there will no any notification for this user.
If you really want the notification when an uninvited user is trying to access your organization, you can try to report a feature request on Developer Community.
That will make it possible for you to interact with the appropriate Product Group, and make it more convenient for the Product Group to collect and categorize your suggestions.
[UPDATED]
When an uninvited user is trying to access a private project in an organization, This user first should gain the access to the organization, then to the project.
So, this user should first get the grant from the PCA (Project Collection Administrators) to access the organization, then get the grant to access the project.
The PCA also can grant users to access any projects in the organization. But the Project Administrators may do not have permissions to grant users to access the organization.
I have followed a tutorial through which i have managed to post on a facebook group using their sdk and graph API on python, on the graph api version 11.
I created a user on facebook, gave it the admin rights of that particular group.
Created an app on facebook, in development mode.
Requested permissions through that app for posting to the relevant group as that user.
Generated extended access token for the same.
Issue: Admins of the group can see the posts, but the normal members of the group cannot.
is it an issue with the app? Does it need to be out of development for the posts created by it to be made visible to others?
Python Code snippet:
import json
from facebook import GraphAPI
access_token= 'access token here'
graph = GraphAPI(access_token)
message = 'This is a test post...hear me'
link = '' #link needs to go here
groups = ['group id here'] #group id
for group in groups:
graph.put_object(group,'feed', message=message,link=link)
print(graph.get_connections(group, 'feed'))
This is mentioned in facebook's documentation.
Whenever an app is created on facebook's developer console, in developer mode, any posts made by the app are not seen by the general public even if you are posting on public groups. Depending on the permissions and what you are trying to accomplish exactly, you might need to go through app review and through business review.
If you don't need to go through the reviews for the permission you have chosen, make sure that the app is in "Live" mode and you will be good to go.
handy feature if they were a bit upfront about it.
I have 2 different Microsoft Teams Accounts that are not linked in any way.
On one account I was able to sideload my bot and if I chat with my Bot in an Teams Channel my bot does Answer. Also it answeres me if I private message it.
On the other account I also sideloaded my bot but my Bot does not react if I message him in an Teams Channel. But it answeres me if I private message it.
I created both bots via App Studio in Teams.
Now I've noticed a difference in App Studio and I think this is why my Bot does not react.
Image of App Studio where the Bot works:
Image of App Studio where the Bot does not work:
The settings in App Studio where the Bot does not work are a bit shorter.
What is happening here? How can I make my Bot work?
Colby's answer might be the fix to you problem, however there are also other permissions settings that you can consider as well, if that doesn't fix it.
I have 2 different Microsoft Teams Accounts that are not linked in any way.
If your accounts are in different organizations, then it's possible that the lack of ability to see your bot that you've added in a Team Channel is due to settings set up by your org's admin. It states here in the Admin settings for apps in Microsoft Teams article in the Important text block:
Be sure you've turned on apps for Teams in Tenant-wide settings in the Microsoft 365 admin center. If you want to add external apps (provided by third parties), you'll need to turn on External apps settings.
From what I can see I think your issue is because the scope on your other bot is set to only Personal. If you click on edit and select "Team" via the Scope section it should fix your issue. Let me know if that helped.
I created and deployed a Node.js bot on my Azure account. I also added the Cortana channel with Manage user identity through Connected Services enabled and Request user profile data enabled (here I have User.Info.Email and User.Info.Name). The bot is shared with multiple people using groups (Deployed to group option in the Cortana dashboard).
If I'm logged-in into Cortana with the same email I use on Azure (where the bot is deployed) I get the auth window (since I enabled Connected Services) and then the following screen.
This is fine since that's how the bot should work.
But if I'm logged-in into Cortana with a different email (one of the emails from the Cortana dashboard group) I don't get the auth window and also some requested permissions are missing.
Are there more steps or requirements for sharing Cortana skills than just using the Deployed to group option?
If you Deploy to Group first, then change your skill configuration, the deployed to group users will only see the first configuration you made.
If I create a blueprint at apiary.io, then grant Editor rights to a few other folks, is there any lingering specialness about "me"?
If so, how can I figure out who "owns" the bp?
In particular, I have created Apiary accounts for several email addresses, and made them all editors. I'm now trying to use the CLI (github: apiaryio/apiary-client). It tells me "403 Forbidden" when I use a token generated (at login.apiary.io/tokens) for several "Editor" accounts. How can I pick the "true owner" account (which, obviously, I've forgot) to try the CLI against?
You can find the owner name in the documentation header on the left, under the API Project name.
For team APIs, that would be the team name, for personal APIs, it's the name of the user.
To answer your initial question, the owner can access and change the API Settings (e.g. change API Project visibility, connect the API Project to GitHub, etc.). Additionaly, if the owner is a member of a team, they can transfer ownership of their personal API Project to the team.