返回 Skill 列表
extension
分类: 开发与工程无需 API Key

perplexity-enterprise-rbac

配置Perplexity企业SSO、基于角色的访问控制和组织管理。在实施SSO集成、配置基于角色的权限或设置Perplexity的组织级控制时使用。可以通过诸如“perplexity SSO”、“perplexity RBAC”、“perplexity 企业”、“perplexity 角色”、“perplexity 权限”、“perplexity SAML”等短语触发。

person作者: jakexiaohubgithub

Perplexity Enterprise RBAC

Overview

Configure enterprise-grade access control for Perplexity integrations.

Prerequisites

  • Perplexity Enterprise tier subscription
  • Identity Provider (IdP) with SAML/OIDC support
  • Understanding of role-based access patterns
  • Audit logging infrastructure

Role Definitions

| Role | Permissions | Use Case | |------|-------------|----------| | Admin | Full access | Platform administrators | | Developer | Read/write, no delete | Active development | | Viewer | Read-only | Stakeholders, auditors | | Service | API access only | Automated systems |

Role Implementation

enum PerplexityRole {
  Admin = 'admin',
  Developer = 'developer',
  Viewer = 'viewer',
  Service = 'service',
}

interface PerplexityPermissions {
  read: boolean;
  write: boolean;
  delete: boolean;
  admin: boolean;
}

const ROLE_PERMISSIONS: Record<PerplexityRole, PerplexityPermissions> = {
  admin: { read: true, write: true, delete: true, admin: true },
  developer: { read: true, write: true, delete: false, admin: false },
  viewer: { read: true, write: false, delete: false, admin: false },
  service: { read: true, write: true, delete: false, admin: false },
};

function checkPermission(
  role: PerplexityRole,
  action: keyof PerplexityPermissions
): boolean {
  return ROLE_PERMISSIONS[role][action];
}

SSO Integration

SAML Configuration

// Perplexity SAML setup
const samlConfig = {
  entryPoint: 'https://idp.company.com/saml/sso',
  issuer: 'https://perplexity.com/saml/metadata',
  cert: process.env.SAML_CERT,
  callbackUrl: 'https://app.yourcompany.com/auth/perplexity/callback',
};

// Map IdP groups to Perplexity roles
const groupRoleMapping: Record<string, PerplexityRole> = {
  'Engineering': PerplexityRole.Developer,
  'Platform-Admins': PerplexityRole.Admin,
  'Data-Team': PerplexityRole.Viewer,
};

OAuth2/OIDC Integration

import { OAuth2Client } from '@perplexity/sdk';

const oauthClient = new OAuth2Client({
  clientId: process.env.PERPLEXITY_OAUTH_CLIENT_ID!,
  clientSecret: process.env.PERPLEXITY_OAUTH_CLIENT_SECRET!,
  redirectUri: 'https://app.yourcompany.com/auth/perplexity/callback',
  scopes: ['read', 'write'],
});

Organization Management

interface PerplexityOrganization {
  id: string;
  name: string;
  ssoEnabled: boolean;
  enforceSso: boolean;
  allowedDomains: string[];
  defaultRole: PerplexityRole;
}

async function createOrganization(
  config: PerplexityOrganization
): Promise<void> {
  await perplexityClient.organizations.create({
    ...config,
    settings: {
      sso: {
        enabled: config.ssoEnabled,
        enforced: config.enforceSso,
        domains: config.allowedDomains,
      },
    },
  });
}

Access Control Middleware

function requirePerplexityPermission(
  requiredPermission: keyof PerplexityPermissions
) {
  return async (req: Request, res: Response, next: NextFunction) => {
    const user = req.user as { perplexityRole: PerplexityRole };

    if (!checkPermission(user.perplexityRole, requiredPermission)) {
      return res.status(403).json({
        error: 'Forbidden',
        message: `Missing permission: ${requiredPermission}`,
      });
    }

    next();
  };
}

// Usage
app.delete('/perplexity/resource/:id',
  requirePerplexityPermission('delete'),
  deleteResourceHandler
);

Audit Trail

interface PerplexityAuditEntry {
  timestamp: Date;
  userId: string;
  role: PerplexityRole;
  action: string;
  resource: string;
  success: boolean;
  ipAddress: string;
}

async function logPerplexityAccess(entry: PerplexityAuditEntry): Promise<void> {
  await auditDb.insert(entry);

  // Alert on suspicious activity
  if (entry.action === 'delete' && !entry.success) {
    await alertOnSuspiciousActivity(entry);
  }
}

Instructions

Step 1: Define Roles

Map organizational roles to Perplexity permissions.

Step 2: Configure SSO

Set up SAML or OIDC integration with your IdP.

Step 3: Implement Middleware

Add permission checks to API endpoints.

Step 4: Enable Audit Logging

Track all access for compliance.

Output

  • Role definitions implemented
  • SSO integration configured
  • Permission middleware active
  • Audit trail enabled

Error Handling

| Issue | Cause | Solution | |-------|-------|----------| | SSO login fails | Wrong callback URL | Verify IdP config | | Permission denied | Missing role mapping | Update group mappings | | Token expired | Short TTL | Refresh token logic | | Audit gaps | Async logging failed | Check log pipeline |

Examples

Quick Permission Check

if (!checkPermission(user.role, 'write')) {
  throw new ForbiddenError('Write permission required');
}

Resources

Next Steps

For major migrations, see perplexity-migration-deep-dive.