Merge pull request #2938 from newrelic/DOC-6138-permissions-callout

Remove handful of old permissions callouts for DOC-6138

src/content/docs/agents/manage-apm-agents/configuration/server-side-agent-configuration.mdx

@@ -42,10 +42,6 @@ For more information about the hierarchy of settings, see the illustration for t
 
 ## Enable server-side configuration [#enable-ssc]
 
-<Callout variant="tip">
-  **Owner, Admins, or [Add-on Managers](/docs/accounts-partnerships/accounts/account-setup/add-roles-permissions)**
-</Callout>
-
 The C SDK and PHP agent do not support server-side configuration. To enable server-side configuration settings for apps that use other New Relic agents:
 
 1. Go to **[one.newrelic.com](https://one.newrelic.com)** and click **APM**.
@@ -55,10 +51,6 @@ After you enable server-side configuration, you can view and change the availabl
 
 ## View or change server-side configuration settings [#customize-ssc]
 
-<Callout variant="tip">
-  **Owner, Admins, or [Add-on Managers](/docs/accounts-partnerships/accounts/account-setup/add-roles-permissions)**
-</Callout>
-
 If you use server-side configuration, you must still include your `license_key` and `app_name` in the local config file. These settings are required for the agent to communicate with the New Relic collector.
 
 The C SDK and PHP agent do not support server-side configuration. To view or change the available server-side configuration settings through the UI for apps that use other New Relic agents:

src/content/docs/agents/manage-apm-agents/configuration/view-config-values-your-app.mdx

@@ -16,8 +16,4 @@ You need an easy way to get information about your application's configuration s
 
 ## Solution
 
-<Callout variant="tip">
-  **Owner**, **Admins**, or **Add-on managers**
-</Callout>
-
 If you do not want to view your configuration file itself, you can view the configuration settings in the APM UI, go to **[one.newrelic.com](https://one.newrelic.com)** and click **APM**. Click your app, then click **Settings > Environment > Agent initialization**.

src/content/docs/agents/python-agent/configuration/python-agent-configuration.mdx

@@ -54,9 +54,6 @@ Here are detailed descriptions of each configuration method:
     id="server-side-configuration"
     title="Server-side configuration"
   >
-    <Callout variant="tip">
-      **Owner or Admins**
-    </Callout>
 
     [Server-side configuration](/docs/agents/manage-apm-agents/configuration/server-side-agent-configuration) allows you to configure certain settings in the New Relic One UI. This applies your changes automatically to all agents even if they run across multiple hosts. Where available, this document includes the UI labels for server-side config under individual config options as the **Server-side label**.
 

src/content/docs/mobile-apps/new-relic-mobile-apps/authentication-alerts/alerting-new-relic-mobile-apps.mdx

@@ -19,10 +19,6 @@ redirects:
   - /docs/mobile-monitoring/new-relic-mobile-apps/mobile-app-features/alerting-new-relic-mobile-apps
 ---
 
-<Callout variant="tip">
-  **Owner or Admins**
-</Callout>
-
 Account administrators can set up configuration to receive push notifications on Android and iOS devices from [New Relic Alerts](/docs/alerts/new-relic-alerts-beta/getting-started/new-relic-alerts). You can receive alerts from any policy by attaching a user channel to the policy.
 
 ## Requirements [#requirements]

src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/configure-proguard-or-dexguard-android-apps.mdx

@@ -11,10 +11,6 @@ redirects:
   - /docs/mobile-monitoring/new-relic-mobile-android/install-configure/installing-android-apps-proguard-dexguard
 ---
 
-<Callout variant="tip">
-  **Admins or Owner**
-</Callout>
-
 Follow these instructions to support ProGuard or DexGuard with New Relic Mobile for Android. Check [our Android compatibility and requirements](/docs/mobile-monitoring/new-relic-mobile-android/get-started/new-relic-android-compatibility-requirements), and if you have previously installed the Android agent SDK for New Relic Mobile, follow the [steps before upgrading](/docs/mobile-apps/android-1-upgrade) to the latest version with ProGuard or DexGuard.
 
 ## Configure ProGuard [#proguard]

src/content/docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrade-new-relic-mobiles-android-sdk.mdx

@@ -13,10 +13,6 @@ redirects:
   - /docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrading-new-relic-mobiles-android-sdk
 ---
 
-<Callout variant="tip">
-  **Owner, Admins, or [add-on managers](/docs/accounts-partnerships/accounts/account-setup/add-roles-permissions)**
-</Callout>
-
 To ensure you have the most current version of New Relic Mobile, see the [Android agent release notes](/docs/release-notes/mobile-release-notes/android-release-notes). Instructions to upgrade your Android app with the latest version of New Relic Mobile will vary, based on which version of the Android agent SDK you are currently using.
 
 ## Upgrade from Android SDK versions 2 or 3 [#android_upgrade_2]

src/content/docs/mobile-monitoring/new-relic-mobile-android/legacy/install-android-apps-android-22-support.mdx

@@ -19,8 +19,4 @@ To support Android 2.2, you must use version [4.244.0](/docs/release-notes/mobil
 
 ## Install with support for older Android version [#installation]
 
-<Callout variant="tip">
-  **Owner, Admins, or [add-on managers](/docs/accounts-partnerships/accounts/account-setup/add-roles-permissions)**
-</Callout>
-
 If you have previously installed a version of the Android SDK for New Relic Mobile, follow the [steps before upgrading](/docs/mobile-monitoring/new-relic-mobile-android/install-configure/upgrade-new-relic-mobiles-android-sdk#android_upgrade_1) to the latest version. Then follow standard [installation and configuration procedures](/docs/mobile-monitoring/new-relic-mobile-android/install-configure) for New Relic Mobile's Android agent.

src/content/docs/mobile-monitoring/new-relic-mobile-ios/tvos/tvos-installation-configuration.mdx

@@ -9,10 +9,6 @@ redirects:
   - /docs/mobile-monitoring/new-relic-mobile-ios/get-started/tvos-installation-configuration
 ---
 
-<Callout variant="tip">
-  **Owner or Admins**
-</Callout>
-
 Follow these instructions to install and configure New Relic Mobile functionality with your tvOS applications.
 
 <Callout variant="tip">

src/content/docs/mobile-monitoring/new-relic-mobile-ios/tvos/upgrading-new-relic-mobiles-tvos-sdk.mdx

@@ -9,10 +9,6 @@ redirects:
   - /docs/mobile-monitoring/new-relic-mobile-ios/install-configure/upgrading-new-relic-mobiles-tvos-sdk
 ---
 
-<Callout variant="tip">
-  **Owner or Admins**
-</Callout>
-
 You must be the account Admin to install, configure, and upgrade New Relic Mobile functionality with your tvOS applications. For information about the latest version, refer to the [release notes](/docs/releases/ios).
 
 ## Contents [#qiklinks]

src/content/docs/using-new-relic/user-interface-functions/share-your-data/ticketing-integrations.mdx

@@ -33,10 +33,6 @@ In addition, Lighthouse setup requires:
 
 ## Integrate with New Relic [#procedures]
 
-<Callout variant="tip">
-  **Owner and Admins**
-</Callout>
-
 To connect your New Relic account to Lighthouse:
 
 1. Go to: **[account dropdown](/docs/using-new-relic/welcome-new-relic/get-started/glossary#account-dropdown) > Account settings > Integrations > Ticketing integrations**.