JavaScriptWebWebNode.jsPhoneGapReactReduxTitaniumVueJavaScript V4 Access Manager API Reference for Realtime AppsNode.js V4 Access Manager API Reference for Realtime AppsPhoneGap V4 Access Manager API Reference for Realtime AppsTitanium V4 Access Manager API Reference for Realtime AppsVue V4 Access Manager API Reference for Realtime Apps

PubNub Access Manager (PAM) allows you to enforce secure controls for client access to resources within the PubNub network. With PAM, your servers can grant their clients access to individual PubNub resources for a limited duration, with the ability to extend access or add permissions for additional resources.

As soon as PAM is enabled, no publish/subscribe operations can be done without first explicitly providing an authorization token to the PubNub object. If an invalid token is provided, the requesting client will receive a Forbidden error.

For more information about PAM, refer to Managing Permissions with Access Manager.

Grant

Privileges specifically granted to an application's subscribeKey always take precedence over privileges granted to channel or auth Key. Therefore an application that requires authentication at the user level should not grant access at either the Application or Channel levels. View the Grant Levels section for more details.

To make granting access on multiple channels and channel groups more efficient, you can use the wildcard notation. It doesn't, however, apply to the uuid resource and you can only go one level deep using wildcards.

• * grants access on all channels
• a.* grants access on all channels that begin with `a.`
• a.b.* doesn't work. If you grant on a.b.*, the grant treats `a.b.*` as a channel name, not a wildcard

1. Application Level - PAM privileges are always evaluated first at the Application level. If either read or write attribute is set to true for a subscribeKey, PAM will immediately grant access for that attribute without proceeding to check permissions at either Channel or User levels. If an attribute is set to false at the Application level, PAM proceeds to evaluate the attribute at the next most granular level.
2. Channel Level - After first verifying an attribute at the Application level, PAM evaluates the attribute at the Channel level. If an attribute is set to true for a combination of subscribeKey, and channel, PAM grants access for that attribute at the Channel level without proceeding to check whether there may be user level permissions.
3. User Level (Recommended) - As a final step PAM evaluates the attributes at the User level. If an attribute is set to true for subscribeKey, channel and auth Key, access is granted for that attribute. Similarly, user level grants also allow you granting an auth Key access to channelGroups and uuids. User level grants require authKeys and are the recommended approach if you need to manage permissions for individual users within your application. Each user should be assigned a unique auth Key and securely passed back to the user to perform operations on the platform.

Method(s)

1. grant( {Array channels, Array channelGroups, Array uuids, Array authKeys, Number ttl, Boolean read, Boolean write, Boolean manage, Boolean delete, Boolean get, Boolean update, Boolean join}, Function callback )

   Parameter	Type	Required	Defaults	Description
   authKeys	Array	Optional		Specifies authKey to grant permissions. It is possible to specify multiple auth keys as comma separated list in combination with a single channel name. authKeys are required for user-level grants. If you don’t specify an authKey, the permissions will apply to all clients on channel-level or application-level. View the Grant Levels section for more details.
   channels	Array	Specifying either channels, channelGroups or uuids is mandatory.		Specifies up to 200 channels on which to grant permissions. Either channels, channelGroups or uuids are required.
   channelGroups	Array	Specifying either channels, channelGroups or uuids is mandatory.		Specifies up to 200 channel groups on which to grant permissions. Either channels, channelGroups or uuids are required.
   uuids	Array	Optional		Specifies up to 200 uuids on which to grant permissions. Either channels, channelGroups or uuids are required.   You can't grant permissions to channels and channel groups in the same request if you decide to use uuids. This parameter does not support wildcards.
   ttl	Number	Yes	1440 (24hrs)	Time in minutes for which granted permissions are valid. Default is 1440 (24hrs), Max is 525600 , Min is 1. Setting ttl to 0 will apply the grant indefinitely.
   read	Boolean	Optional	false	Set to true to grant read permissions. Set to false to remove permissions.
   write	Boolean	Optional	false	Set to true to grant write permissions. Set to false to remove permissions.
   manage	Boolean	Optional	false	Set to true to grant manage permissions. Set to false to remove permissions.
   delete	Boolean	Optional	false	Set to true to grant delete permissions. Set to false to remove permissions.
   get	Boolean	Optional	false	Set to true to grant get permissions. Set to false to remove permissions.
   update	Boolean	Optional	false	Set to true to grant update permissions. Set to false to remove permissions.
   join	Boolean	Optional	false	Set to true to grant join permissions. Set to false to remove permissions.
   callback	Function	Optional		Executes on a successful/unsuccessful grant.

Basic Usage

pubnub.grant(
    {
        authKeys: ['my_authkey'],
        channels: ['my_channel'],
        ttl: 12313, // 0 for infinite
        read: true, // false to disallow
        write: true, // false to disallow
        manage: true, // false to disallow
        delete: true // false to disallow
    },
    function (status) {
        // handle state setting response
    }
);

{
    "status" : 200,
    "message" : "Success",
    "payload" : {
        "ttl" : 1440,
        "auths" : {
            "my_authkey" : {
                "r" : 1,
                "w" : 1,
                "m" : 1,
                "d" : 1,
                "g" : 0,
                "u" : 0,
                "j" : 0
            }
        },
        "subscribe_key" : "my_subkey",
        "level" : "user",
        "channel" : "my_channel"
    },
    "service" : "Access Manager"
}

Other Examples

1. Grant subscribe privileges to all users on all channel(s) with default ttl (1440 minutes):

   // grant world read access to all channels
   
   pubnub.grant({
       read: true
   });
   

2. Allow subscribe and publish to a specific channel for all users (no auth Key required) with default ttl (1440 minutes):

   pubnub.grant(
       {
           channels: ['my_channel'],
           read: true, // false to disallow
           write: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

3. Grant subscribe access to a channel only for clients with a specific auth Key with a 5 minute ttl:

   pubnub.grant(
       {
           channels: ['my_channel'],
           authKeys: ['my_ro_authkey'],
           ttl: 5, // 0 for infinite
           read: true, // false to disallow
           write: false // false to disallow
       }, 
       function (status) {
           console.log(status);
       }
   );

   The above code would return the following response to the client:

   {
       error: false,
       operation: 'PNAccessManagerGrant',
       statusCode: 200
   }

4. Allow access to a specific channel for Presence:

   pubnub.grant(
       {
           channels: ['my_channel-pnpres'],
           ttl: 5, // 0 for infinite
           read: true, // false to disallow
           write: true // false to disallow
       }, 
       function (status) {
           console.log(status);
       }
   );

5. Allow access to all channel groups using wildcard:
   To perform a first level wildcard grant for channel groups you need to specify : (colon) as the parameter for channelGroups. This will ensure that users can read or manage all channel groups.

   pubnub.grant(
       {
           channelGroups: [':'],
           read: true, 
           manage: true
       },
       function (status) {
           console.log(status);
       }
   );

6. Grant access to all channels on all authKeys

   This request grants read permission to all users on all channel(s) with default ttl (1440 minutes). This rule applies on the application level and takes precedence over channel and user-level permissions.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

   pubnub.grant({
       read: true
   });
   

7. Channel Level Grant

   pubnub.grant(
       {
           channels: ['ch1'],
           read: true, // false to disallow
           write: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

8. Grant access to a channel on an authKey

   Grant read permission to a channel only for clients with a specific authKey with a 5 minute ttl:

   pubnub.grant(
       {
           authKeys: ['my_authkey'],
           channels: ['my_channel'],
           read: true, // false to disallow
           write: false // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

9. UUID Level Grant

   pubnub.grant(
       {
           uuids: ['uuid1'],
           authKeys: ['key1'],
           ttl: 60, // 0 for infinite
           get: true, // false to disallow
           update: true, // false to disallow
           delete: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

PubNub Access Manager (PAM) extends PubNub's existing security framework by allowing developers to create and enforce secure access to channels and channel groups throughout the PubNub Real-Time Network.

As soon as Access Manager is enabled, no pub/sub-operations can be done without first explicitly providing an authorization token to the PubNub object. If an invalid token is provided, the requesting client will receive a Forbidden Error.

Learn more about Access Manager here.

Grant

Description

1. Application level privileges are based on subscribeKey applying to all associated channels.
2. Channel level privileges are based on a combination of subscribeKey and channel name.
3. User level privileges are based on the combination of subscribeKey, channel and auth Key.

1. Application Level - PAM privileges are always evaluated first at the Application level. If either read or write attribute is set to true for a subscribeKey, PAM will immediately grant access for that attribute without proceeding to check permissions at either Channel or User levels. If an attribute is set to false at the Application level, PAM proceeds to evaluate the attribute at the next most granular level.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

2. Channel Level - After first verifying an attribute at the Application level, PAM evaluates the attribute at the Channel level. If an attribute is set to true for a combination of subscribeKey and channel, PAM grants access for that attribute at the Channel level without proceeding to check whether there may be user level permissions.
3. User Level - As a final step PAM evaluates the attributes at the User level. If an attribute is set to true for subscribeKey, channel and auth Key, access is granted for that attribute.

• History: To access historical messages you must grant full read access at either the subscribeKey or channel level. When a user has the appropriate permissions they can access any data stored. If they do not have access a 403 will be returned by PAM.
• Presence: To grant access to Presence for a particular channel name you must also allow read and write access to the presence channel name which is specified by adding the -pnpres suffix to the name. Also note that a leave will fail in the case where a user's grant expires while connected. An HTTP 403 will be returned.
• APNs: Standard permissions are required for publishing.

Method(s)

1. grant({Array channels, Array channelGroups, Array uuids, Array authKeys, Number ttl, Boolean read, Boolean write, Boolean manage, Boolean delete, Boolean get, Boolean update, Boolean join},Function callback)

   Parameter	Type	Required	Defaults	Description
   authKeys	Array	Optional		Specifies authKey to grant permissions. It is possible to specify multiple auth keys as comma separated list in combination with a single channel name. authKeys are required for user-level grants. If you don’t specify an authKey, the permissions will apply to all clients on channel-level or application-level. View the Grant Levels section for more details.
   channels	Array	Specifying either channels or channelGroups is mandatory.		Specifies the channels on which to grant permissions. If no channels/channelGroups are specified, then the grant applies to any and all channels/channelGroups that have been or will be created for that publish/subscribe key set. Furthermore, any existing or future grants on specific channels are ignored, until the all channels grant is revoked. It is possible to grant permissions to multiple channels simultaneously by specifying the channels as a comma separated list. Wildcard notation like a.* can be used to grant access on channels. You can grant one level deep. a.* - you can grant on this. a.b.* - grant will not work on this. If you grant on a.b.*, the grant will treat a.b.* as a single channel with name a.b.*.
   channelGroups	Array	Specifying either channels or channelGroups is mandatory.		Specifies the channelGroups to grant permissions. If no channels/channelGroups are specified, then the grant applies to any and all channels/channelGroups that have been or will be created for that publish/subscribe key set. Furthermore, any existing or future grants on specific channelGroups are ignored, until the all channelGroups grant is revoked. It is possible to grant permissions to multiple channelGroups simultaneously by specifying the channelGroups as a comma separated list.
   uuids	Array	Optional		A list of uuids to grant permissions to. You can't grant permissions to channels and channel groups in the same request if you decide to use uuids. This parameter does not support wildcards.
   ttl	Number	Yes	1440 (24hrs)	Time in minutes for which granted permissions are valid. Default is 1440 (24hrs), Max is 525600 , Min is 1. Setting ttl to 0 will apply the grant indefinitely.
   read	Boolean	Optional	false	Read permissions are granted by setting to true. Read permissions are removed by setting to false.
   write	Boolean	Optional	false	Write permissions are granted by setting to true. Write permissions are removed by setting to false.
   manage	Boolean	Optional	false	Manage permissions are granted by setting to true. Manage permissions are removed by setting to false.
   delete	Boolean	Optional	false	Set to true to grant delete permissions. Set to false to remove delete permissions.
   get	Boolean	Optional	false	Set to true to grant get permissions. Set to false to remove get permissions.
   update	Boolean	Optional	false	Set to true to grant update permissions. Set to false to remove update permissions.
   join	Boolean	Optional	false	Set to true to grant join permissions. Set to false to remove join permissions.
   callback	Function	Optional		Executes on a successful/unsuccessful grant.

Basic Usage

pubnub.grant(
    {
        authKeys: ['my_authkey'],
        channels: ['my_channel'],
        ttl: 12313, // 0 for infinite
        read: true, // false to disallow
        write: true, // false to disallow
        manage: true, // false to disallow
        delete: true // false to disallow
    },
    function (status) {
        // handle state setting response
    }
);

Other Examples

1. Grant subscribe privileges to all users on all channel(s) with default ttl (1440 minutes):

   // grant world read access to all channels
   
   pubnub.grant({
       read: true
   });
   

2. Allow subscribe and publish to a specific channel for all users (no auth Key required) with default ttl (1440 minutes):

   pubnub.grant(
       {
           channels: ['my_channel'],
           read: true, // false to disallow
           write: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

3. Grant subscribe access to a channel only for clients with a specific auth Key with a 5 minute ttl:

   pubnub.grant(
       {
           channels: ['my_channel'],
           authKeys: ['my_ro_authkey'],
           ttl: 5, // 0 for infinite
           read: true, // false to disallow
           write: false // false to disallow
       }, 
       function (status) {
           console.log(status);
       }
   );

   The above code would return the following response to the client:

   {
       error: false,
       operation: 'PNAccessManagerGrant',
       statusCode: 200
   }

4. Allow access to a specific channel for Presence:

   pubnub.grant(
       {
           channels: ['my_channel-pnpres'],
           ttl: 5, // 0 for infinite
           read: true, // false to disallow
           write: true // false to disallow
       }, 
       function (status) {
           console.log(status);
       }
   );

5. Allow access to all channel groups using wildcard:
   To perform a first level wildcard grant for channel groups you need to specify : (colon) as the parameter for channelGroups. This will ensure that users can read or manage all channel groups.

   pubnub.grant(
       {
           channelGroups: [':'],
           read: true, 
           manage: true
       },
       function (status) {
           console.log(status);
       }
   );

6. Grant access to all channels on all authKeys

   This request grants read permission to all users on all channel(s) with default ttl (1440 minutes). This rule applies on the application level and takes precedence over channel and user-level permissions.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

   pubnub.grant({
       read: true
   });
   

7. Channel Level Grant

   pubnub.grant(
       {
           channels: ['ch1'],
           read: true, // false to disallow
           write: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

8. Grant access to a channel on an authKey

   Grant read permission to a channel only for clients with a specific authKey with a 5 minute ttl:

   pubnub.grant(
       {
           authKeys: ['my_authkey'],
           channels: ['my_channel'],
           read: true, // false to disallow
           write: false // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

9. UUID Level Grant

   pubnub.grant(
       {
           uuids: ['uuid1'],
           authKeys: ['key1'],
           ttl: 60, // 0 for infinite
           get: true, // false to disallow
           update: true, // false to disallow
           delete: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

PubNub Access Manager (PAM) extends PubNub's existing security framework by allowing developers to create and enforce secure access to channels and channel groups throughout the PubNub Real-Time Network.

As soon as Access Manager is enabled, no pub/sub-operations can be done without first explicitly providing an authorization token to the PubNub object. If an invalid token is provided, the requesting client will receive a Forbidden Error.

Learn more about Access Manager here.

Grant

Description

1. Application level privileges are based on subscribeKey applying to all associated channels.
2. Channel level privileges are based on a combination of subscribeKey and channel name.
3. User level privileges are based on the combination of subscribeKey, channel and auth Key.

1. Application Level - PAM privileges are always evaluated first at the Application level. If either read or write attribute is set to true for a subscribeKey, PAM will immediately grant access for that attribute without proceeding to check permissions at either Channel or User levels. If an attribute is set to false at the Application level, PAM proceeds to evaluate the attribute at the next most granular level.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

2. Channel Level - After first verifying an attribute at the Application level, PAM evaluates the attribute at the Channel level. If an attribute is set to true for a combination of subscribeKey and channel, PAM grants access for that attribute at the Channel level without proceeding to check whether there may be user level permissions.
3. User Level - As a final step PAM evaluates the attributes at the User level. If an attribute is set to true for subscribeKey, channel and auth Key, access is granted for that attribute.

• History: To access historical messages you must grant full read access at either the subscribeKey or channel level. When a user has the appropriate permissions they can access any data stored. If they do not have access a 403 will be returned by PAM.
• Presence: To grant access to Presence for a particular channel name you must also allow read and write access to the presence channel name which is specified by adding the -pnpres suffix to the name. Also note that a leave will fail in the case where a user's grant expires while connected. An HTTP 403 will be returned.
• APNs: Standard permissions are required for publishing.

Method(s)

1. grant({Array channels, Array channelGroups, Array uuids, Array authKeys, Number ttl, Boolean read, Boolean write, Boolean manage, Boolean delete, Boolean get, Boolean update, Boolean join},Function callback)

   Parameter	Type	Required	Defaults	Description
   authKeys	Array	Optional		Specifies authKey to grant permissions. It is possible to specify multiple auth keys as comma separated list in combination with a single channel name. authKeys are required for user-level grants. If you don’t specify an authKey, the permissions will apply to all clients on channel-level or application-level. View the Grant Levels section for more details.
   channels	Array	Specifying either channels or channelGroups is mandatory.		Specifies the channels on which to grant permissions. If no channels/channelGroups are specified, then the grant applies to any and all channels/channelGroups that have been or will be created for that publish/subscribe key set. Furthermore, any existing or future grants on specific channels are ignored, until the all channels grant is revoked. It is possible to grant permissions to multiple channels simultaneously by specifying the channels as a comma separated list. Wildcard notation like a.* can be used to grant access on channels. You can grant one level deep. a.* - you can grant on this. a.b.* - grant will not work on this. If you grant on a.b.*, the grant will treat a.b.* as a single channel with name a.b.*.
   channelGroups	Array	Specifying either channels or channelGroups is mandatory.		Specifies the channelGroups to grant permissions. If no channels/channelGroups are specified, then the grant applies to any and all channels/channelGroups that have been or will be created for that publish/subscribe key set. Furthermore, any existing or future grants on specific channelGroups are ignored, until the all channelGroups grant is revoked. It is possible to grant permissions to multiple channelGroups simultaneously by specifying the channelGroups as a comma separated list.
   uuids	Array	Optional		A list of uuids to grant permissions to. You can't grant permissions to channels and channel groups in the same request if you decide to use uuids. This parameter does not support wildcards.
   ttl	Number	Yes	1440 (24hrs)	Time in minutes for which granted permissions are valid. Default is 1440 (24hrs), Max is 525600 , Min is 1. Setting ttl to 0 will apply the grant indefinitely.
   read	Boolean	Optional	false	Read permissions are granted by setting to true. Read permissions are removed by setting to false.
   write	Boolean	Optional	false	Write permissions are granted by setting to true. Write permissions are removed by setting to false.
   manage	Boolean	Optional	false	Manage permissions are granted by setting to true. Manage permissions are removed by setting to false.
   delete	Boolean	Optional	false	Set to true to grant delete permissions. Set to false to remove delete permissions.
   get	Boolean	Optional	false	Set to true to grant get permissions. Set to false to remove get permissions.
   update	Boolean	Optional	false	Set to true to grant update permissions. Set to false to remove update permissions.
   join	Boolean	Optional	false	Set to true to grant join permissions. Set to false to remove join permissions.
   callback	Function	Optional		Executes on a successful/unsuccessful grant.

Basic Usage

pubnub.grant(
    {
        channels: ['my_channel'],
        authKeys: ['my_rw_authkey'],
        read: true,
        write: true,
        ttl: 5
    },
    function (status) {
        // handle state setting response
    }
);

Other Examples

1. Grant subscribe privileges to all users on all channel(s) with default ttl (1440 minutes):

   // grant world read access to all channels
   
   pubnub.grant({
       read: true
   });
   

2. Allow subscribe and publish to a specific channel for all users (no auth Key required) with default ttl (1440 minutes):

   // grant world read/write to myChannel
   
   pubnub.grant(
       {
           channels: ['my_channel'],
           read: true,
           write: true
       },
       function (status) {
           console.log(status);
       }
   );

3. Grant subscribe access to a channel only for clients with a specific auth Key with a 5 minute ttl:

   // allow user read only access to myChannel
   
   pubnub.grant(
       {
           channels: ['my_channel'],
           authKeys: ['my_ro_authkey'],
           ttl: 5,
           read: true,
           write: false
       },
       function (status) {
           console.log(status);
       }
   );

   The above code would return the following response to the client:

   {
       error: false,
       operation: 'PNAccessManagerGrant',
       statusCode: 200
   }

4. Allow access to a specific channel for Presence:

   // Allow world read / write access to myChannel-pnpres
   
   pubnub.grant(
       {
           channels: ['my_channel-pnpres'],
           ttl: 5,
           read: true,
           write: true
       },
       function (status) {
           console.log(status);
       }
   );

5. Allow access to all channel groups using wildcard:
   To perform a first level wildcard grant for channel groups you need to specify : (colon) as the parameter for channelGroups. This will ensure that users can read or manage all channel groups.

   pubnub.grant(
       {
           channelGroups: [':'],
           read: true, 
           manage: true
       },
       function (status) {
           console.log(status);
       }
   );

6. Grant access to all channels on all authKeys

   This request grants read permission to all users on all channel(s) with default ttl (1440 minutes). This rule applies on the application level and takes precedence over channel and user-level permissions.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

   pubnub.grant({
       read: true
   });
   

7. Channel Level Grant

   pubnub.grant(
       {
           channels: ['ch1'],
           read: true, // false to disallow
           write: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

8. Grant access to a channel on an authKey

   Grant read permission to a channel only for clients with a specific authKey with a 5 minute ttl:

   pubnub.grant(
       {
           authKeys: ['my_authkey'],
           channels: ['my_channel'],
           read: true, // false to disallow
           write: false // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

9. UUID Level Grant

   pubnub.grant(
       {
           uuids: ['uuid1'],
           authKeys: ['key1'],
           ttl: 60, // 0 for infinite
           get: true, // false to disallow
           update: true, // false to disallow
           delete: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );

PubNub Access Manager (PAM) extends PubNub's existing security framework by allowing developers to create and enforce secure access to channels and channel groups throughout the PubNub Real-Time Network.

As soon as Access Manager is enabled, no pub/sub-operations can be done without first explicitly providing an authorization token to the PubNub object. If an invalid token is provided, the requesting client will receive a Forbidden Error.

Learn more about Access Manager here.

Grant

Description

1. Application level privileges are based on subscribeKey applying to all associated channels.
2. Channel level privileges are based on a combination of subscribeKey and channel name.
3. User level privileges are based on the combination of subscribeKey, channel and auth Key.

1. Application Level - PAM privileges are always evaluated first at the Application level. If either read or write attribute is set to true for a subscribeKey, PAM will immediately grant access for that attribute without proceeding to check permissions at either Channel or User levels. If an attribute is set to false at the Application level, PAM proceeds to evaluate the attribute at the next most granular level.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

2. Channel Level - After first verifying an attribute at the Application level, PAM evaluates the attribute at the Channel level. If an attribute is set to true for a combination of subscribeKey and channel, PAM grants access for that attribute at the Channel level without proceeding to check whether there may be user level permissions.
3. User Level - As a final step PAM evaluates the attributes at the User level. If an attribute is set to true for subscribeKey, channel and auth Key, access is granted for that attribute.

• History: To access historical messages you must grant full read access at either the subscribeKey or channel level. When a user has the appropriate permissions they can access any data stored. If they do not have access a 403 will be returned by PAM.
• Presence: To grant access to Presence for a particular channel name you must also allow read and write access to the presence channel name which is specified by adding the -pnpres suffix to the name. Also note that a leave will fail in the case where a user's grant expires while connected. An HTTP 403 will be returned.
• APNs: Standard permissions are required for publishing.

Method(s)

1. grant({Array channels, Array channelGroups, Array uuids, Array authKeys, Number ttl, Boolean read, Boolean write, Boolean manage, Boolean delete, Boolean get, Boolean update, Boolean join},Function callback)

   Parameter	Type	Required	Defaults	Description
   authKeys	Array	Optional		Specifies authKey to grant permissions. It is possible to specify multiple auth keys as comma separated list in combination with a single channel name. authKeys are required for user-level grants. If you don’t specify an authKey, the permissions will apply to all clients on channel-level or application-level. View the Grant Levels section for more details.
   channels	Array	Specifying either channels or channelGroups is mandatory.		Specifies the channels on which to grant permissions. If no channels/channelGroups are specified, then the grant applies to any and all channels/channelGroups that have been or will be created for that publish/subscribe key set. Furthermore, any existing or future grants on specific channels are ignored, until the all channels grant is revoked. It is possible to grant permissions to multiple channels simultaneously by specifying the channels as a comma separated list. Wildcard notation like a.* can be used to grant access on channels. You can grant one level deep. a.* - you can grant on this. a.b.* - grant will not work on this. If you grant on a.b.*, the grant will treat a.b.* as a single channel with name a.b.*.
   channelGroups	Array	Specifying either channels or channelGroups is mandatory.		Specifies the channelGroups to grant permissions. If no channels/channelGroups are specified, then the grant applies to any and all channels/channelGroups that have been or will be created for that publish/subscribe key set. Furthermore, any existing or future grants on specific channelGroups are ignored, until the all channelGroups grant is revoked. It is possible to grant permissions to multiple channelGroups simultaneously by specifying the channelGroups as a comma separated list.
   uuids	Array	Optional		A list of uuids to grant permissions to. You can't grant permissions to channels and channel groups in the same request if you decide to use uuids. This parameter does not support wildcards.
   ttl	Number	Yes	1440 (24hrs)	Time in minutes for which granted permissions are valid. Default is 1440 (24hrs), Max is 525600 , Min is 1. Setting ttl to 0 will apply the grant indefinitely.
   read	Boolean	Optional	false	Read permissions are granted by setting to true. Read permissions are removed by setting to false.
   write	Boolean	Optional	false	Write permissions are granted by setting to true. Write permissions are removed by setting to false.
   manage	Boolean	Optional	false	Manage permissions are granted by setting to true. Manage permissions are removed by setting to false.
   delete	Boolean	Optional	false	Set to true to grant delete permissions. Set to false to remove delete permissions.
   get	Boolean	Optional	false	Set to true to grant get permissions. Set to false to remove get permissions.
   update	Boolean	Optional	false	Set to true to grant update permissions. Set to false to remove update permissions.
   join	Boolean	Optional	false	Set to true to grant join permissions. Set to false to remove join permissions.
   callback	Function	Optional		Executes on a successful/unsuccessful grant.

Basic Usage

import PubNubVue from 'pubnub-vue';

const pubnub = PubNubVue.getInstance();

pubnub.grant(
    {
        channels: [ch1, ch2],
        channelGroups: [cg1, cg2],
        authKeys: [key1, key2],
        ttl: 12313, // 0 for infinite
        read: true, // false to disallow
        write: true, // false to disallow
        manage: true// false to disallow
    },
    function(status) {
        // handle state setting response
    }
);

Other Examples

1. Grant subscribe privileges to all users on all channel(s) with default ttl (1440 minutes):

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   // grant world read access to all channels
    
   pubnub.grant({
       read: true
   });

2. Allow subscribe and publish to a specific channel for all users (no auth Key required) with default ttl (1440 minutes):

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   pubnub.grant(
       {
           channels: ['my_channel'],
           read: true, // false to disallow
           write: true// false to disallow
       },
       function(status) {
           console.log(status);
       }
   );

3. Grant subscribe access to a channel only for clients with a specific auth Key with a 5 minute ttl:

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   pubnub.grant(
       {
           channels: ['my_channel'],
           authKeys: ['my_ro_authkey'],
           ttl: 5, // 0 for infinite
           read: true, // false to disallow
           write: false// false to disallow
       },
       function(status) {
           console.log(status);
       }
   );

   The above code would return the following response to the client:

   {
       error: false,
       operation: 'PNAccessManagerGrant',
       statusCode: 200
   }

4. Allow access to a specific channel for Presence:

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   pubnub.grant(
       {
           channels: ['my_channel-pnpres'],
           ttl: 5, // 0 for infinite
           read: true, // false to disallow
           write: true// false to disallow
       }, 
       function(status) {
           console.log(status);
       }
   );

5. Allow access to all channel groups using wildcard:
   To perform a first level wildcard grant for channel groups you need to specify : (colon) as the parameter for channelGroups. This will ensure that users can read or manage all channel groups.

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   pubnub.grant(
       {
           channelGroups: [':'],
           read: true, 
           manage: true
       },
       function(status) {
           console.log(status);
       }
   );

6. Grant access to all channels on all authKeys

   This request grants read permission to all users on all channel(s) with default ttl (1440 minutes). This rule applies on the application level and takes precedence over channel and user-level permissions.

   Use application level grants with caution When access is granted on an application level, all channels and users will have access. Application level grants can also happen due to a bug in your code. e.g. Null parameters for channels and auth-keys can cause accidental application level grants.

   pubnub.grant({
       read: true
   });
   

7. Channel Level Grant

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   pubnub.grant(
       {
           channels: ['ch1'],
           read: true, // false to disallow
           write: true// false to disallow
       },
       function(status) {
           console.log(status);
       }
   );

8. Grant access to a channel on an authKey

   Grant read permission to a channel only for clients with a specific authKey with a 5 minute ttl:

   import PubNubVue from 'pubnub-vue';
   
   const pubnub = PubNubVue.getInstance();
   
   pubnub.grant(
       {
           channels: ['ch1'],
           authKeys: ['key1'],
           read: true, // false to disallow
           write: true// false to disallow
       },
       function(status) {
           console.log(status);
       }
   );

9. UUID Level Grant

   pubnub.grant(
       {
           uuids: ['uuid1'],
           authKeys: ['key1'],
           ttl: 60, // 0 for infinite
           get: true, // false to disallow
           update: true, // false to disallow
           delete: true // false to disallow
       },
       function (status) {
           console.log(status);
       }
   );