Nami Public Documentation
Sign In
Nami Documentation
Nami Documentation
  • Get Started
    • Overview
      • Key Concepts
      • Data Collection
      • Built for Privacy
    • Evaluating Nami
    • SDKs
      • Apple Native SDK
      • Android Native SDK
      • Amazon Native SDK
      • Roku Native SDK
      • React Native Cross-Platform SDK
      • Flutter Cross-Platform SDK
      • Unity Cross-Platform SDK
      • Release Notes
        • Find Nami SDK Version
    • Quickstart Guide
  • Subscription Management
    • Overview
    • Products
      • Archive Products
      • Sync Products
    • Entitlements
    • Customer Screen
    • Accounts and Login/Logout
    • Advanced Use Cases
      • Upgrades and Downgrades
      • Supported Purchase Change States by Platform
      • Restoring Purchases
      • Working with Consumable IAPs
  • No Code Paywalls
    • Overview
    • Paywall Creator
      • Using the Creator
      • Paywall Layout
      • Components
        • Editing, Deleting, Reordering
        • Hiding Components
        • Video
        • Collapse
      • Editable Properties
        • Focused Styling
        • Safe Area
      • Conditions
        • Notched Devices
        • Product Entitlements
      • Adding Products
      • Repeating Product Group
      • Product Fields
      • Capabilities
        • Featured Styling
        • Selected Styling
        • Custom Brand Fonts
        • Carousel
        • Trial Eligibility
        • Deeplink Button
        • Introductory Offer Eligibility
        • Login Check
        • Product Groups
        • Conditional Product Groups
        • Offer Eligibility and Purchasing
        • Screenreader Text
        • Personalization Tokens
        • Custom Variables
        • Multipage
        • Custom Data Source
        • Advanced Video Features
        • Product Error States
      • ❓FAQs
        • Designing Paywalls in Figma
        • Guide to Building a Paywall from Scratch
      • 🎁Releases
        • Roadmap
    • Paywall Templates
      • Pacific
      • Pacific Premium
      • Trident
      • Starfish
      • Mantis
      • Venice
      • Venice Premium
      • Honest
      • Catalina
      • Oyster
      • Puffin
      • Marina
      • Beluga
      • Driftwood
      • Lagoon
      • Pisces
      • Aquarius
      • Conch
      • Lionfish
      • Moray
      • Tetra
      • Lighthouse
      • Puffin Tablet
    • Managing Paywalls
      • Archiving a Paywall
      • Duplicate a Paywall
    • Paywall Smart Text
    • Pricing Eligibility States
    • Pricing Eligibility by Platform
    • Nami Paywalls in Different Languages
    • Legacy Paywalls
  • Campaigns
    • Placements
      • Create a Placement
      • Deeplink Placements
      • Archiving a Placement
      • Managing Lots of Placements
      • Export Placements
    • Campaigns
      • Campaign Filters
        • Campaign Use Cases
      • Archiving a Campaign
      • Scheduling a Campaign
      • Campaign Conversion Events
      • Managing Lots of Campaigns
      • Campaign Troubleshooting
    • A/B and Multivariate Testing
      • Selecting an A/B test winner
      • A/B Test Allocation
  • Integrations
    • All Integrations
    • Billing Platforms
      • Apple Integration
        • App Store Setup
          • Privacy Details
        • Platform Integration
        • App Store Server Notifications
        • Store Credentials
          • App Store Connect Shared Secret
          • Apple App Store Connect API
          • Apple In App Purchase
        • Add a Product
        • Platform Sync
        • SDK Integration
        • Troubleshooting
        • Testing and Development
          • Apple Testing Environments
          • Setting up Device Sandbox Test Environment
          • Setting up StoreKit config in Xcode
      • Google Integration
        • Google Play Store Setup
        • Platform Integration
        • Service Account
        • Real-time Developer Notifications
        • Add a Product
        • Platform Sync
        • SDK Setup
        • Troubleshooting
          • Supporting Android minSdkVersion 25 or lower
          • Requested product is not available for purchase
          • Unsupported Version of Play Billing
      • Amazon Appstore Integration
        • Create Amazon Android App
        • Platform Integration
        • Shared Key
        • Real-time Event Notifications
        • Add a Product
        • SDK Integration
        • Testing
      • Roku Integration
        • Platform Integration
        • API Key
        • Transaction Notifications
        • Add a Product
        • SDK Integration
      • Web Integration
    • Analytics Tools
      • Adobe Analytics
      • Amplitude
      • Google Analytics
      • mParticle
      • 3rd-Party Analytics
    • Subscription Management
      • Nami Subscription Management
      • Bring your Own Payment Code
    • CDP Integrations
      • Adobe CDP Integration
      • Amplitude CDP Integration
      • Custom CDP Integration
      • Generic CDP Integration
    • Other Integrations
      • Wicket Labs
      • Webhooks
        • Introduction to the Nami ML Event System
        • Event Types
          • Purchase Status Updates
          • Events for Upgrades, Downgrades, and Crossgrades
        • Event Subscriptions
        • Understanding Transferred Events and Accounts
      • API Access
    • Events Feed
  • Analytics
    • Using Charts
    • Paywall Analytics
      • Impressions
      • Paywall Conversion Rate
      • Sessions
      • Active Devices
    • Subscription Analytics
      • Revenue
      • MRR
      • Purchases
      • Trial Starts
  • Nami Account
    • Manage your Apps
      • Find your Nami App Platform ID
      • Setting up Legal Text for your Apps
    • Organization
      • Configuring Organization Security Policies
      • Billing
    • Invite your Team
      • Roles
    • Manage your Account
      • Two-Factor Authentication (2FA)
Powered by GitBook
On this page
  • Expire Passwords
  • Lockout Team Members After Failed Login Attempts
  • Disable Inactive Team Members
  • Control Center Sessions
  1. Nami Account
  2. Organization

Configuring Organization Security Policies

Last updated 11 months ago

📘 Organization Security Policies are part of our Enterprise plans. Please if you are interested in this feature.

A number of configurable security policies are available that apply to all members of your organization.

To access policies, go to and click the Security Policies tab. Admins will see a new Policies section that contains all new organizational security policy settings. Only admins can manage these policies.

Expire Passwords

This policy ensures that team member passwords get reset frequently.

This policy is configured as the number of days between password reset.

Instructions

  1. Toggle on the switch to the right of ‘Expire Passwords’ in the Policies section

  2. You will see a field appear called ‘Expiration Time in Days’

  3. Set this field to the desired number of days, such as 90

  4. Click Update Policies at the bottom of the page to Save

Lockout Team Members After Failed Login Attempts

This policy will lock out a team member if they fail too many times to login, as a prevention against hackers or brute force attacks.

This policy requires 3 values: the number of failed attempts that are allowed (X), the amount of time allotted to successfully login in minutes (Y), and the amount of time that the team member will be locked out of their account if they fail to login in minutes (Z).

Instructions

  1. Toggle on the switch to the right of ‘Lockout Team Members After Failed Login Attempts’ in the Policies section

  2. You will see 3 fields appear

  3. Fill out values for X Failed Attempts, Y Minutes, and Z Minutes Locked Out. Sample values would be 6, 10, and 3. (6 Failed Attempts in 10 Minutes Results in 3 Minute Account Lockout) Click Update Policies at the bottom of the page to Save

Disable Inactive Team Members

This policy ensures that team members are logging into the Nami Control Center regularly, and that inactive team member accounts aren’t vulnerable.

This policy is configured in days.

Instructions

  1. Toggle on the switch to the right of ‘Disable Inactive Team Members’ in the Policies section

  2. You will see a new field appear called ‘Inactivity Time Period in Days’

  3. Enter a value for the Inactivity Time Period, such as 90 days

  4. Click Update Policies at the bottom of the page to Save

Control Center Sessions

There are 2 values governing how long team Nami Control Center member sessions are. Inactive Session Length refers to how long a team member can be inactive on their device before the system logs them out. Max Session Length refers to the total session length a team member can have, regardless of activity.

Both values are configured in minutes. Nami sets defaults for these session values, but you can configure them to be shorter.

For an example: the Inactive Session Length is 10 minutes and the Max Session Length is 20 minutes. A team member logs in on their browser and then checks email for 10 minutes, leaving the Nami Control Center open but inactive in another tab. When they return to the Nami Control Center, they will have been logged out. However another team member logs in on their browser and works in the Nami Control Center for 20 minutes straight. After 20 minutes, the Control Center logs them out and requires them to log in again, even though they have been active.

Instructions

  1. Navigate to the bottom of the Policies section

  2. Inactive Session Length is set by default to 14 days, or 20160 minutes. To change this policy, set this value to a lower number such as 30 minutes.

  3. Max Session Length is set by default to 14 days, or 20160 minutes. To change this policy, set this value to a lower number such as 90 minutes.

  4. Click Update Policies at the bottom of the page to Save

Max Session Length must be greater than or equal to Inactive Session Length

contact us
Org Settings