The majority of the add-ins in the Office Store are level ReadWriteDocument with almost all add-ins supporting at least the ReadDocument level. A five-level JavaScript API access-permissions model provides the basis for privacy and security for users of task pane add-ins. To interact with the user's document, the add-in needs to declare what permission it needs in the manifest. Read and write data to and from a user's document to provide value to that user.įor more information about the types and capabilities of Office Add-ins, see Office Add-ins platform overview, especially the section "Anatomy of an Office Add-in." Read a user's document to provide contextual services. Office Add-ins combine an XML manifest file that contains some metadata about the add-in, but most importantly points to a web application which contains all the code and logic. In some situations, you might want to restrict access to a small set of users by making assignments to specific users by assigning users manually. As an admin, you might find it easier to manage add-ins by using groups and controlling the membership of those groups rather than assigning individual users each time. However, we recommend making assignments by using groups. The right option for your organization depends on your configuration. Just me If you assign an add-in to just yourself, the add-in is assigned to only your account, which is ideal for testing the add-in. In either case, no additional action is required from the admin. When a user is removed from a group, the user loses access to the add-in. Groups If you assign an add-in to a group, users who are added to the group are automatically assigned the add-in. Users If you assign an add-in to an individual user, and then deploy the add-in to a new user, you must first add the new user. Use this option sparingly and only for add-ins that are truly universal to your organization. Each option has implications:Įveryone This option assigns the add-in to every user in the organization. Global admins and Exchange admins can assign an add-in to everyone or to specific users and groups. Include or link to Help content or FAQs that might help users if they have problems with the add-in.Ĭonsiderations when assigning an add-in to users and groups Consider sending an email that describes when and how to use the add-in. It's good practice to inform users and groups that the deployed add-in is available. If you've deployed the add-in to other members of your organization, follow the instructions to announce the deployment of the add-in. If you've deployed to just yourself, you can select Change who has access to add-in to deploy to more users. Outlook add-ins can take up to 24 hours to appear on app ribbons. Users might need to relaunch Microsoft 365 to view the add-in icon on the app ribbon. Select Deploy Add-in at the top of the page, and then select Next. In the admin center, go to the Settings > Integrated apps > Add-ins page. Deploy an Office Add-in using the admin centerīefore you begin, see Determine if Centralized Deployment of add-ins works for your organization. Again, evaluate the results and, if successful, continue with full deployment.ĭepending on the size of the target audience, you can add or remove roll-out steps. Roll out the add-in to more individuals within the business. If the deployment is successful, move to step 2. Roll out the add-in to a small set of business stakeholders and members of the IT department. To roll out add-ins by using a phased approach, we recommend the following: Recommended approach for deploying Office Add-ins For Outlook use Exchange control panel to deploy in an on-premises environment without a connection to Microsoft 365. For Word, Excel and PowerPoint use a SharePoint App Catalog to deploy add-ins to users in an on-premises environment with no connection to Microsoft 365 and/or support for SharePoint add-ins required.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |